Fix: Keep equal sign for empty query parameters[INS-4228]#7802
Merged
Fix: Keep equal sign for empty query parameters[INS-4228]#7802
Conversation
|
|
2.Update related unit test
filfreire
force-pushed
the
fix/equal-sign-for-empty-query-parameters
branch
from
add4f4e to
c892e5f
Compare
filfreire
approved these changes
Aug 5, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Relates to #2111
Add a strictNullHandling option for smartEncodeUrl.
By default, query string with equal sign(&foo=) or without equal sign(&foo) will converted to empty string as search param value.
When this option is enabled, with equal sign(&foo=) will parsed as empty string in search param value while without equal sign(&foo) will parsed as null in search param value. After all, we can distinguish the different between two situations.
Also update the querystring unit test.