You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Andi Huber (Jira)" <ji...@apache.org> on 2022/04/29 17:57:00 UTC

[jira] [Closed] (ISIS-1672) Simplify handling of autoComplete facet, by copying autoComplete from parameter type's spec down to the parameter itself

     [ https://issues.apache.org/jira/browse/ISIS-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andi Huber closed ISIS-1672.
----------------------------
    Resolution: Won't Fix

won't fix: I think we have more than one place where we need to check for facets on the parameter argument and facets on the parameter type; think its not strictly required to start making inferred facets for all these cases; keep it simple 

> Simplify handling of autoComplete facet, by copying autoComplete from parameter type's spec down to the parameter itself
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-1672
>                 URL: https://issues.apache.org/jira/browse/ISIS-1672
>             Project: Isis
>          Issue Type: Improvement
>          Components: Isis Core
>    Affects Versions: 1.14.0
>            Reporter: Daniel Keir Haywood
>            Priority: Minor
>
> Currently ReferencePanel and (as of ISIS-1600) the  ActionChoicesForCollectionParameterFacetFactory both check for autoComplete/choices of a parameter in two places:
> a) on the parameter itself (as per a choicesNXxx() or an autoCompleteNXxx())
> b) on the parameter's type (as per @DomainObject(autoCompleteRepository=...)
> To simplify and make more consistent, should derive a parameter-level ActionParameterAutoCompleteFacet from the objectspec's AutoCompletefacet.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)