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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(URL): Share link with search parameters #173
base: main
Are you sure you want to change the base?
feat(URL): Share link with search parameters #173
Changes from 4 commits
10656aa
ae155bf
6647961
d398cee
d4398aa
7761079
7d446bd
a8224ba
c4aa866
a2a9b2c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel some of these handlings shall be done in the UrlContextProvider instead:
queryString
,isCaseSensitive
andisRegex
from the URL search parameters, can we expectqueryParams.queryString
,queryParams.isCaseSensitive
andqueryParams.isRegex
instead?queryParams.isCaseSensitive
andqueryParams.isRegex
are false when they are absent in the URL? i.e., shall we consider making those parameters optional?queryString
,isCaseSensitive
andisRegex
directly from the UrlContextProvider, can we expose a single objectqueryParams
? That way in the StateContextProvider code, we can simply check ifqueryParams
is null.