-
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 - set default value for tag controls #431
Conversation
right now, field.default_value gets initialized to 0 for every DialogFieldTagControl. What should be happening: - single selects: <Choose>/<None> gets shown as default - multiselects: Nothing selected same as the other dropdowns and multidropdowns. Thus changing the initialization to set either "" or [] as default_value.
Checked commit https://github.com/himdel/ui-components/commit/2a74e2452ad80a64fdfd72655d8569fd84269896 with ruby 2.5.5, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0 |
(kicking stuck travis; the core dependency is merged now) |
We need this in ivanchuk for https://bugzilla.redhat.com/show_bug.cgi?id=1859524 Although this will most likely require an ivanchuk-specific PR, since this probably won't cherry-pick cleanly. |
Dialog User - set default value for tag controls (cherry picked from commit a47b131) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1859524
Ivanchuk backport details:
|
right now, field.default_value gets initialized to 0 for every DialogFieldTagControl.
What should be happening:
<Choose>
/<None>
gets shown as defaultNothing selected
same as the other dropdowns and multidropdowns.
Thus changing the initialization to set either "" or [] as default_value.
Fixes ManageIQ/manageiq-ui-classic#6392
May depend on ManageIQ/manageiq#19696
and ManageIQ/manageiq#19697