-
Notifications
You must be signed in to change notification settings - Fork 52
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
dialog-user: Move tagging fix from #412 to setDefaultValue #414
Conversation
The dialogField component should not be changing default_value, the dialogData service is the place where default_value gets set. https://bugzilla.redhat.com/show_bug.cgi?id=1729379
Checked commit https://github.com/himdel/ui-components/commit/403703b65ff20b3225ba5e35ab06f747718cbfc6 with ruby 2.4.6, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0 |
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.
LGTM 👍, thank you for the correction @himdel
dialog-user: Move tagging fix from #412 to setDefaultValue (cherry picked from commit b224a50) https://bugzilla.redhat.com/show_bug.cgi?id=1749061
Hammer backport details:
|
@himdel realizing now, that we don't allow setting a default value for Tag Control in Dialog Editor, the test |
dialog-user: Move tagging fix from #412 to setDefaultValue (cherry picked from commit b224a50) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1767836
Ivanchuk backport details:
|
(follow-up to #412)
The dialogField component should not be changing default_value,
the dialogData service is the place where default_value gets set.
Otherwise, validations from dialog-user and from dialog-field will work with different values, which can cause invalid validations or validation loops.
(docs - https://github.com/ManageIQ/manageiq-ui-classic/wiki/Dialogs#dialog-user-tidbits)
https://bugzilla.redhat.com/show_bug.cgi?id=1729379
Cc @romanblanco @h-kataria