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
fix(router): remove preserveQueryParams symbol #38762
fix(router): remove preserveQueryParams symbol #38762
Conversation
ec0e0f5
to
8ac7f8f
Compare
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.
LGTM, but would add blocked label to wait for the migration PR to merge.
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.
This one has been deprecated for a long time, so it's great that we are removing it!
Do we understand the impact of this change? it's likely low, but we should verify. I see at least two instances in google3, I haven't tried to search github.
If a migration was part of this PR then this change would be totally fine, but I get that creating migrations for absolutely everything doesn't always makes sense const/benefits-wise. Maybe get @mgechev to weigh in on skipping a migration?
If we are not going to create a migration for this change, then we should at least document the decision in the PR with a brief justification, something along the lines: "This api has been deprecated for a long time, and we don't have evidence that it's being used.
And additionally we should highlight this change in the v11 release notes / update guide.
Otherwise lgtm.
@@ -117,13 +116,6 @@ Tip: In the [API reference section](api) of this doc site, deprecated APIs are i | |||
| --- | ----------- | --------------------- | ----- | | |||
| [`ngModel` with reactive forms](#ngmodel-reactive) | [`FormControlDirective`](api/forms/FormControlDirective) | v6 | none | | |||
|
|||
{@a router} |
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.
instead of deleting this section, can you please move it to the removed apis section: https://angular.io/guide/deprecations#removed-apis-1
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.
Please update the deprecations.md as mentioned above. thanks!
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.
Reviewed-for: public-api
LGTM after @IgorMinar's comments are addressed.
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.
Reviewed-for: public-api
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.
just resubmitting #38762 (review) to get this out of my review queue for now
Reviewed-for: public-api, docs-packaging-and-releasing
5f96a67
to
d00a610
Compare
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.
just a few nits, the rest looks good.
packages/core/schematics/test/preserve_query_params_migration_spec.ts
Outdated
Show resolved
Hide resolved
packages/core/schematics/test/preserve_query_params_migration_spec.ts
Outdated
Show resolved
Hide resolved
packages/core/schematics/test/preserve_query_params_migration_spec.ts
Outdated
Show resolved
Hide resolved
packages/core/schematics/test/preserve_query_params_migration_spec.ts
Outdated
Show resolved
Hide resolved
packages/core/schematics/migrations/router-preserve-query-params/README.md
Outdated
Show resolved
Hide resolved
@@ -117,13 +116,6 @@ Tip: In the [API reference section](api) of this doc site, deprecated APIs are i | |||
| --- | ----------- | --------------------- | ----- | | |||
| [`ngModel` with reactive forms](#ngmodel-reactive) | [`FormControlDirective`](api/forms/FormControlDirective) | v6 | none | | |||
|
|||
{@a router} |
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.
Please update the deprecations.md as mentioned above. thanks!
Remove preserveQueryParams as it was deprecated for removal in v4, use queryParamsHandling="preserve" instead. BREAKING CHANGE: preserveQueryParams has been removed, use queryParamsHandling="preserve" instead
Create a schematic for migrating preserveQueryParams to use queryParamsHandler instead.
d00a610
to
7f9a836
Compare
Updates the removed section in the deprecations guide to talk about APIs removed in v11 rather than the pervious versions.
7f9a836
to
d19677b
Compare
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.
LGTM! Thanks!
Reviewed-for: public-api
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.
Reviewed-for: global-approvers, docs-packaging-and-releasing, dev-infra,
Create a schematic for migrating preserveQueryParams to use queryParamsHandler instead. PR Close #38762
Updates the removed section in the deprecations guide to talk about APIs removed in v11 rather than the pervious versions. PR Close #38762
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Remove preserveQueryParams as it was deprecated for removal in v4, use
queryParamsHandling="preserve" instead.