-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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(platform-browser): enable HTTP request caching when using provideClientHydration
#49699
Conversation
/** | ||
* Disables DOM nodes reuse during hydration. Effectively makes | ||
* Angular re-render an application from scratch on the client. | ||
* | ||
* @publicApi | ||
* @developerPreview | ||
*/ | ||
export function withoutDomReuse(): NoDomReuseFeature { | ||
export function withoutDomReuse(): HydrationFeature<HydrationFeatureKind.NoDomReuseFeature> { |
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.
Are HydrationFeature
and HydrationFeatureKind
really needed to be part of the public API? In @angular/common/http
I noticed they are but was wondering what they are needed.
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 followed the typings that we have in the Router, but I'm ok with this option too 👍
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.
Should they still be exported?
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.
Yeah, we need to export them.
9c21736
to
1541f5d
Compare
a6ede8b
to
df6bd17
Compare
Caretaker note: this requires a G3 patch and BUILD file to be updated. http://cl/521719612 The broken target seems to be caused by other changes in the presubmit CL. |
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, just a quick question on the API.
/** | ||
* Disables DOM nodes reuse during hydration. Effectively makes | ||
* Angular re-render an application from scratch on the client. | ||
* | ||
* @publicApi | ||
* @developerPreview | ||
*/ | ||
export function withoutDomReuse(): NoDomReuseFeature { | ||
export function withoutDomReuse(): HydrationFeature<HydrationFeatureKind.NoDomReuseFeature> { |
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 followed the typings that we have in the Router, but I'm ok with this option too 👍
…deClientHydration` This commit adds support by default for HTTP caching when using `provideClientHydration`. Users can opt-out of this behaviour by using the `withoutHttpTransferCache` feature. ```ts import { bootstrapApplication, provideClientHydration, withNoHttpTransferCache, } from '@angular/platform-browser'; // ... bootstrapApplication(RootCmp, { providers: [provideClientHydration(withNoHttpTransferCache())] }); ```
df6bd17
to
9e4365c
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.
@alan-agius4 looks great! 👍
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.
reviewed-for: fw-core, fw-http, fw-platform-server, public-api
Caretaker notes:
|
This PR was merged into the repository by commit 81e7d15. |
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. |
This commit adds support by default for HTTP caching when using
provideClientHydration
. Users can opt-out of this behaviour by using thewithoutHttpTransferCache
feature.