Adjust how default_value is calculated for multi-select drop downs #17449
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Somewhat related to this PR, but will clean up some of the specs and attempt to force the
default_value
for multiselect drop downs to behave consistently.https://bugzilla.redhat.com/show_bug.cgi?id=1576288
Basically, with this change, multiselects driven by automate domains should behave slightly differently. Before, you could select a "nil" value, but that doesn't really make too much sense when you're dealing with a multiselect, because you will have to unselect the nil value after you pick another value. So instead of a nil value being selected, nothing will be selected.
Also, with this fix, within automate, the user can set their default values in a few ways:
@himdel I know this was kinda messy before, hopefully this cleans it up a bit. Think you can review quickly so this can get in for the build?
@d-m-u Can you review please?
@miq-bot add_label gaprindashvili/yes, bug, blocker
@miq-bot assign @gmcculloug