-
Notifications
You must be signed in to change notification settings - Fork 46
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
FORMS-867: Export CSV submission columns issue (new validation for 'form' keyword in fieldnames) #1033
Conversation
@@ -529,6 +532,18 @@ export default { | |||
this.addPatchToHistory(); | |||
} | |||
} | |||
this.canSave = true; | |||
modified?.components?.map((comp) => { | |||
if (comp.key === 'form') { |
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.
My concern here is that it's a breaking change. A form that was fine before this PR will produce an error when edited and saved after this PR, even if there are no changes to the form.
Maybe this isn't a big deal - how hard would it be to identify how many forms already in production use "form" as one of the field names? Maybe we could work with those form owners to fix their forms before the change.
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.
@WalterMoar there are only 2 published forms which have form
as a field name, should we just notify them?
Description
This PR is to fix use cases when user would name one of the fields as
form
which is system keyword, so we added additional validation so users can't use this API name for fieldsTypes of changes
Bug fix (non-breaking change which fixes an issue)
Checklist
Further comments