Changing how inputs with Array attributes are generated. #1523
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.
Purpose
Related #1518
Description
We already treat the param names ending with
[]
as an array, but right now, there's no way to tell your input that it's an array without manually updating the name. This PR looks at the field, and if it's an Array type, we can append[]
to the name. This required a few things to change since these would call field.param which would just callvalue.to_s
if it was nil. In the case of an array, this would make the value of the input"[]"
.Now we can keep track of how many times you call the attribute which allows us to set a different value for all of the array values you have.
Note
I've tagged this as "BREAKING CHANGE" because this will change how your forms will work when you have arrays. The other major deal is Avram still doesn't handle pulling in values from array params.
Checklist
crystal tool format spec src
./script/setup
./script/test