[
https://issues.apache.org/jira/browse/ISIS-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768870#comment-13768870
]
ASF subversion and git services commented on ISIS-503:
------------------------------------------------------
Commit d82f3d3c7655f9a825a070f0f9cd3aa5e189b2c3 in branch refs/heads/master
from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=d82f3d3 ]
ISIS-478,ISIS-503: various fixes.
ISIS_478, for conditional choices, for EntitySelect:
* clear link now should work
* if no choices/autocomplete then doesn't NPE (BankMandates#newBankMandate)
* removed ID_ENTITY_TITLE_NULL label, since never visible
* sets up a placeholder text
for conditional choices, for ValueSelect:
* correctly initializes second dropdown based
ISIS-503, for contributee actions/associations, calculate identifier
* was causing stack trace when go back to list, caused by call to
getIdentifier() incorrectly returning the wrong value for a contributed
association.
> Refactor the way that members are ordered to allow contributee actions to be
> ordered within regular actions
> ------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-503
> URL: https://issues.apache.org/jira/browse/ISIS-503
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: core-1.2.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: core-1.3.0
>
>
> Currently ordering is done on FacetedMethods, and contributee actions are
> grafted onto the end. Also complicating matters is the ObjectActionSet,
> which groups contributee actions according to the service that contributed
> them.
> First change is to remove ObjectActionSet, and have everything flattened.
> Second change is to rework MemberLayoutArranger such that it acts upon
> ObjectMembers rather than FacetedMethods.
> At same time, suggest retire the old "actionOrder()" supporting method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
