Update 'autoStoreData' feature to support object notation input names #385
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.
Sometimes it's useful to utilise URL encoding in the name of form inputs when routing. For example:
Using
user[name]
as the value for the input's name attribute means that in ExpressJS when using bodyParser (like the prototyping kit) we can do the following in a routes file:user[name]
becomesuser.name
but the autoStoreData feature doesn't account for that.The pull request should deal with that. Removing
_unchecked
from the created objects that get sent back when using 'urlencoded' input names described above and allowing the 'checked' method to deal with those input names.This is a starter. Feedback and improvements welcome but this gets the ball rolling.