-
-
Notifications
You must be signed in to change notification settings - Fork 798
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
[legacy-framework] Change useParam
/ useParams
to always return undefined
for empty/invalid values instead of ""
and NaN
(patch)
#1491
Merged
kodiakhq
merged 5 commits into
blitz-js:canary
from
KATT:feature/return-strict-or-undefined
Nov 24, 2020
Merged
[legacy-framework] Change useParam
/ useParams
to always return undefined
for empty/invalid values instead of ""
and NaN
(patch)
#1491
kodiakhq
merged 5 commits into
blitz-js:canary
from
KATT:feature/return-strict-or-undefined
Nov 24, 2020
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
KATT
commented
Nov 20, 2020
2 tasks
KATT
commented
Nov 20, 2020
@@ -64,6 +64,10 @@ export interface CancellablePromise<T> extends Promise<T> { | |||
|
|||
export type QueryFn = (...args: any) => Promise<any> | |||
|
|||
export type Dict<T> = Record<string, T | undefined> |
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.
Shortcut to writing Record<string, string|undefined>
etc
Iguanya
approved these changes
Nov 23, 2020
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.
well that's helpful
Awesome, thanks @KATT!! |
flybayer
changed the title
Refactor
Change Nov 24, 2020
useParam
/ useParams
useParam
/ useParams
to always return undefined
for empty/invalid values instead of ""
and NaN
(patch)
flybayer
approved these changes
Nov 24, 2020
itsdillon
changed the title
Change
[legacy-framework] Change Jul 7, 2022
useParam
/ useParams
to always return undefined
for empty/invalid values instead of ""
and NaN
(patch)useParam
/ useParams
to always return undefined
for empty/invalid values instead of ""
and NaN
(patch)
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.
Related: blitz-js/legacy-framework#616 #1474
What are the changes and their implications?
params[key]
useParam
with number will never returnNaN
Checklist.