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
refactor(platform-browser): remove withNoDomReuse
function
#52057
Conversation
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!
reviewed-for: fw-core, fw-platform-server, 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.
LGTM
Reviewed-for: public-api
30947f2
to
9d06b67
Compare
This commit removes the `withNoDomReuse` function to minimize public API. The `withNoDomReuse` function used to disable DOM reuse, which is the main feature of the `provideClientHydration()`. The `withNoDomReuse()` function was in the "developer preview" mode, so the removal happens without prior deprecation. BREAKING CHANGE: The `withNoDomReuse()` function was removed from the public API. If you need to disable hydration, you can exclude the `provideClientHydration()` call from provider list in your application (which would disable hydration features for the entire application) or use `ngSkipHydration` attribute to disable hydration for particular components. See this guide for additional information: https://angular.io/guide/hydration#how-to-skip-hydration-for-particular-components.
9d06b67
to
69cab96
Compare
Caretaker notes:
|
This PR was merged into the repository by commit dbc14eb. |
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. |
…#52057) This commit removes the `withNoDomReuse` function to minimize public API. The `withNoDomReuse` function used to disable DOM reuse, which is the main feature of the `provideClientHydration()`. The `withNoDomReuse()` function was in the "developer preview" mode, so the removal happens without prior deprecation. BREAKING CHANGE: The `withNoDomReuse()` function was removed from the public API. If you need to disable hydration, you can exclude the `provideClientHydration()` call from provider list in your application (which would disable hydration features for the entire application) or use `ngSkipHydration` attribute to disable hydration for particular components. See this guide for additional information: https://angular.io/guide/hydration#how-to-skip-hydration-for-particular-components. PR Close angular#52057
This commit removes the
withNoDomReuse
function to minimize public API. ThewithNoDomReuse
function used to disable DOM reuse, which is the main feature of theprovideClientHydration()
.The
withNoDomReuse()
function was in the "developer preview" mode, so the removal happens without prior deprecation.BREAKING CHANGE:
The
withNoDomReuse()
function was removed from the public API. If you need to disable hydration, you can exclude theprovideClientHydration()
call from provider list in your application (which would disable hydration features for the entire application) or usengSkipHydration
attribute to disable hydration for particular components. See this guide for additional information: https://angular.io/guide/hydration#how-to-skip-hydration-for-particular-components.PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?