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
Dynamic data 2 - Auto UI #1293
Dynamic data 2 - Auto UI #1293
Conversation
c08c3ff
to
f6e5c73
Compare
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.
Nice 👍.
The most important comment I have is that the name Dynamic Data
is still used all over the codebase. Most importantly, MD files, exception messages and metadata in csprojs. These should be changed as they are observable by users.
return this; | ||
} | ||
|
||
public PropertyDisplayMetadataModifier Enable(bool allowEdit = true) |
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.
This feels a bit strange in connection with method EnableIfAuthenticated
. The other method automatically sets the value to true
. Either this one should behave similarly, or we should probably rename it to something more descriptive.
public PropertyDisplayMetadataModifier Enable(bool allowEdit = true) | |
public PropertyDisplayMetadataModifier SetAllowEditing(bool value = true) |
DynamicEntity sample also refactored
EnumComboBoxFormEditorProvider added
And fixed bugs in DynamicEditor sample
Concrete DynamicEntity type should be used instead.
Fix replacing of controls which don't allow children Fix styleContext.Property(c => c.P) for binding properties
Fixed issue in control tests
On dynamic data resource bindings it's actually not needed, but it was super annoying trying to make sure it's set correctly in grid, ...
…endering the corresponding fields
+ Configuration text output fixed because of new properties
No description provided.