Skip to content

Conversation

@joelvdgraaf
Copy link

  • Added disable input based on security
  • Upgrade test project to 6.9.1

- Added disable input based on security
- Upgrade test project to 6.9.1
@lindski
Copy link
Contributor

lindski commented May 8, 2018

Hi, this is great, thanks very much

Is there a particular reason why you made this configurable in the widget rather than always making it disabled if the attribute was read only?

@joelvdgraaf
Copy link
Author

In my particular case there was a complex business rule whether the input should be editable/disabled which is only in some pages was checked. In the current implementation there is a virtual attribute in the domain model to give the check and I don't want any virtual attributes at all cost.
That's why I added the 'disabled by microflow' function to check only on those pages if the widget should be editable/disabled to have the best optimized performance..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants