You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 6, 2021. It is now read-only.
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
The reason will be displayed to describe this comment to others. Learn more.
Seems like it's possible for this code could provide unexpected results for self._store. For example, if url ends with a ?. Also, if all search parameters are integers, then self._store would be an array.
I think it would be safest to initialize it to an empty object in all cases:
self._store = {};
if (searchString) {
urlParams = searchString.split("&");
urlParams.forEach(function (param) {
p = param.split("=");
self._store[decodeURIComponent(p[0])] = decodeURIComponent(p[1]);
});
}
The reason will be displayed to describe this comment to others. Learn more.
If the constructor made the call to parse() and parse() was private method, then I would agree. But parse() is public and can be called multiple times.
It occurred to me as I was updating the edge cases that this code doesn't have any exception handling for seriously malformed URLs. Do you want me to address those cases as well or is this sufficient for now?
this code doesn't have any exception handling for seriously malformed URLs
Seems like this code should only handle "url params" (hence the name), so I think it's outside of the scope of this module, and don't need to worry about it.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
2 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.
This is a fix for issue #6008. It also adds remove() and isEmpty() methods to the UrlParams module.