DEVPROD-7765: Provide specific types for parsing query params #543
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
DEVPROD-7765
Description
This bug is caused by our usage of the
query-stringlibrary. We use the{ parseNumbers: true }setting when making calls to this library. So if the filter is a large number, the library will try to parse it out, which JavaScript cannot handle.I updated the library to get access to the new
typesproperty inParserOptions. This property enables enforcing types on each query parameter. The docs say it takes precedence over other properties likeparseNumbersbut I couldn't get that to work, so I just setparseNumbersto false.Testing