Closed himdel closed 5 years ago
Hammer backport details:
$ git log -1
commit d934145909d7973395c70b568980a5200b632b37
Author: Harpreet Kataria <hkataria@redhat.com>
Date: Wed Sep 4 15:00:12 2019 -0400
Merge pull request #414 from himdel/fix412
dialog-user: Move tagging fix from #412 to setDefaultValue
(cherry picked from commit b224a5079f8e86de77e8ebc7c5cdace16b993355)
https://bugzilla.redhat.com/show_bug.cgi?id=1749061
@himdel realizing now, that we don't allow setting a default value for Tag Control in Dialog Editor, the test (defaultValue === undefined)
seems to be unnecessary to me, and I feel like we can just set the defaul_value
on 0
every time.
Ivanchuk backport details:
$ git log -1
commit 32c18f92db1a30f15f33e02aaf50d11e7f984541
Author: Harpreet Kataria <hkataria@redhat.com>
Date: Wed Sep 4 15:00:12 2019 -0400
Merge pull request #414 from himdel/fix412
dialog-user: Move tagging fix from #412 to setDefaultValue
(cherry picked from commit b224a5079f8e86de77e8ebc7c5cdace16b993355)
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1767836
(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