You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2012/12/17 10:34:13 UTC
[jira] [Closed] (ISIS-258) Extend @Hidden and @Disabled to specify
Where the object member should be hidden/disabled.
[ https://issues.apache.org/jira/browse/ISIS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood closed ISIS-258.
----------------------------
prior to generating 1.0.0 release notes
> Extend @Hidden and @Disabled to specify Where the object member should be hidden/disabled.
> ------------------------------------------------------------------------------------------
>
> Key: ISIS-258
> URL: https://issues.apache.org/jira/browse/ISIS-258
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.2.0-incubating
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: isis-1.0.0
>
>
> Coming from a desire to hide property members within tables.
> @Hidden(Where.COLLECTION_TABLE)
> public String getSomeNotVeryInterestingProperty() { ... }
> NB: as a result of this change, will slightly break the applib annotation for both @Hidden and @Disabled.
> For example, previously we had @Hidden(When.UNTIL_PERSISTED), with the value() attribute being set. value() has now been renamed to when(), in order to allow where() to also be added.
> This will now be @Hidden(when=When.UNTIL_PERSISTED).
> Note that @Hidden and @Disabled (by itself, with value() not specified) will continue to work with no changes to application code.
--
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