-
Notifications
You must be signed in to change notification settings - Fork 1
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
fix: #692 Admin FOM should not be editable when commenting open. #693
fix: #692 Admin FOM should not be editable when commenting open. #693
Conversation
So my main concern is that we're changing a number of fields to be only editable in initial state when they were editable in multiple states before. So what if these fields still need to be editable when commenting is closed? I'm not saying they need to be, but it isn't clear what change we are actually making, versus just making fields non-editable during commenting-open. |
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.
I don't have things setup locally to test these but the code looks good!
I had a state here to control the inputs depends on whether the form is in "comment open" state |
Thanks Basil! I adjusted the change, some fields are editable during commenting closed according to latest discussion from Julius. |
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.
Have some questions...
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.
One more approval!
ref: #692
Business requirement changes due to issue the licenses edit FOM during commenting open (description field) and it has legal consequence. New rule: All FOM fields should not be editable except attachments fields during commenting open.
Thanks for the PR!
Any successful deployments (not always required) will be available below.
Once merged, code will be promoted and handed off to following workflow run.
Thanks for the PR!
Any successful deployments (not always required) will be available below.
Once merged, code will be promoted and handed off to following workflow run.