Support DISCLOSURE_LIST form field #3394
Merged
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.
This adds support for a new field with type
DISCLOSURE_LIST
. It's a collapsible / expandable section of nested fields, which are all always sent to the sever (in contrast toTABS
, where only the active tab is sent), and it's a "creatable" list, meaning theDISCLOSURE_LIST
field can be used for a single disclosure section, but it allows adding additional disclosure sections by clicking a plus button. The value sent to the backend is always an array of disclosuresArray<{ [fieldname: string]: unknown }>
Also, this