We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Repeatable fields use dots in the name. While this is convenient for compound fields, this becomes a problem for repeatable fields:
e.g.
name.0
The problem here is that the index is included in the name. What if someone added this field, using javascript:
name.0 name.100
This would lead to an array of 101 elements, having 99 elements with value "undef".
or if someone - in a list of 3 items - deletes one field in the middle of a list:
name.0 name.1 => this one is deleted, but you'll still get an array with three elements, one being "undef" name.2
Rails solves this by adding "[]" after the name. That way the server decides the index value, not the client.
Can this be changed, or is it already available somewhere?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Repeatable fields use dots in the name. While this is convenient for compound fields, this becomes a problem for repeatable fields:
e.g.
The problem here is that the index is included in the name. What if someone added this field, using javascript:
This would lead to an array of 101 elements, having 99 elements with value "undef".
or if someone - in a list of 3 items - deletes one field in the middle of a list:
e.g.
Rails solves this by adding "[]" after the name. That way the server decides the index value, not the client.
Can this be changed, or is it already available somewhere?
The text was updated successfully, but these errors were encountered: