[4.x] Improve array fieldtype validation for dynamically keyed fields #9834
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.
I noticed this little oddity when working on #9632, since we use array fieldtype in new sites configuration UI.
Before this PR, if you try to save a publish form with an array fieldtype that is set to
dynamic
mode, if you leave an empty key or value, you get weird data saved to your yaml:If you use
keyed
orsingle
modes, key and value are both required for each submitted row. This PR adds validation to ensure you properly fill out each row.