-
Notifications
You must be signed in to change notification settings - Fork 160
WIP: dynamic UI.Hidden annotation #456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
| /** | ||
| * Example of a custom handler for nextSiblingAction | ||
| */ | ||
| @Profile("hybrid") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think in other areas we are using cloud
| Label : '{i18n>Contents}', | ||
| Target : 'contents/@UI.PresentationVariant' | ||
| Target : 'contents/@UI.PresentationVariant', | ||
| ![@UI.Hidden] : contentsHidden |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if we can also refer to a Singleton entity here.
| public class SetHiddenHandler implements EventHandler { | ||
|
|
||
| @After(entity = Books_.CDS_NAME) | ||
| void removeUIHidden(EventContext context){ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you should be able to use Result in the method signature.
|
Replaced by #460 which however still runs into a UI bug. Did you observe the same UI issues with this approach? Edit: Bug seems to be avoided by avoiding $Not in the expression. |
Replaces #456 by using a singleton, instead of adding a property to books.
No description provided.