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: add flag for dialog reconfigure #440
dialog-user: add flag for dialog reconfigure #440
Conversation
@@ -49,6 +50,7 @@ export class DialogFieldController { | |||
public setup() { | |||
this.clonedDialogField = _.cloneDeep(this.field); | |||
this.dialogField = this.service.setupField(this.field); | |||
this.dialogField.disabled = this.reconfigureMode && !this.dialogField.reconfigurable; |
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.
Can a field be disabled from automate?
I think this bit should only set disabled=true, but not overwrite with false if already present, if ^.
Otherwise LGTM :)
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.
Fixed (as discussed privately).
0bc9a0a
to
f23d891
Compare
Checked commit mzazrivec@f23d891 with ruby 2.5.7, rubocop 0.69.0, haml-lint 0.28.0, and yamllint |
Thanks, LGTM :) |
…gure dialog-user: add flag for dialog reconfigure (cherry picked from commit 5e79adf) https://bugzilla.redhat.com/show_bug.cgi?id=1837410
…gure dialog-user: add flag for dialog reconfigure (cherry picked from commit 5e79adf)
Jansa backport details:
|
Ivanchuk backport details:
|
In case a dialog is being reconfigured, we need to honor the non-reconfigurable field flag and disable the respective input field.
@himdel
https://bugzilla.redhat.com/show_bug.cgi?id=1837410