Checking that URL params that do not exist in a form will not break functionality of code #42
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…form, then elementsByName[name] is undefined, which breaks $.each function and any code that goes after deserialization
|
Just ran in to this issue, PR addressed it. Thanks! |
|
@nettiopsu thanks for the contribution. can you write a test case for this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
If a query string contains a parameter which is not represented in a form, then elementsByName[name] is undefined, which breaks$.each function and any code that goes after deserialization will not be started ($ .each function can not accept undefined parameters, as it contains undefined.length statement)