-
-
Notifications
You must be signed in to change notification settings - Fork 12
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: 🎸 added option to handle prev/next button in the browser #31
base: master
Are you sure you want to change the base?
Conversation
Run & review this pull request in StackBlitz Codeflow. |
Please add test |
const { queryKey } = def; | ||
const queryParamValue = queryParams.get(queryKey); | ||
|
||
if (!queryParamValue) continue; |
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.
removed.
When using updateOn: 'submit'
, need to clear form controls to prev state
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.
Why removed? can you please elaborate? I don't understand from your comment
@@ -50,8 +50,8 @@ export class QueryParamDef<QueryParams = any> { | |||
return serializedValue === '[object Object]' ? JSON.stringify(controlValue) : serializedValue; | |||
} | |||
|
|||
parse(queryParamValue: string) { | |||
if (this.parser) { | |||
parse(queryParamValue: string | null) { |
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.
do not pass null(undefined) values to custom parser function. Otherwise it causes breaking changes
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'm not sure I understand your comment, why do you need this change?
@NetanelBasal done |
@shaharkazaz please check this |
:) |
@akaNightmare didn't forget that, I'm on vacation 😀 |
parse(queryParamValue: string) { | ||
if (this.parser) { | ||
parse(queryParamValue: string | null) { | ||
if (this.parser && queryParamValue != null) { |
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.
if (this.parser && queryParamValue != null) { | |
if (this.parser && queryParamValue !== null) { |
@@ -50,8 +50,8 @@ export class QueryParamDef<QueryParams = any> { | |||
return serializedValue === '[object Object]' ? JSON.stringify(controlValue) : serializedValue; | |||
} | |||
|
|||
parse(queryParamValue: string) { | |||
if (this.parser) { | |||
parse(queryParamValue: string | null) { |
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'm not sure I understand your comment, why do you need this change?
const { queryKey } = def; | ||
const queryParamValue = queryParams.get(queryKey); | ||
|
||
if (!queryParamValue) continue; |
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.
Why removed? can you please elaborate? I don't understand from your comment
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
closes #13