Skip to content

docs: update event replay section of the hydration guide - #71120

Merged
kirjs merged 1 commit into
angular:mainfrom
GabeSilvaDev:docs/hydration-event-replay-default
Oct 2, 2026
Merged

kirjs merged 1 commit into
angular:mainfrom
GabeSilvaDev:docs/hydration-event-replay-default

Conversation

@GabeSilvaDev

Copy link
Copy Markdown
Contributor

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.dev application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

The "Capturing and replaying events" section of the hydration guide says event replay must be enabled with provideClientHydration(withEventReplay()).

Since #68092 (v22), incremental hydration is enabled by default by provideClientHydration(), and it includes withEventReplay(). The incremental hydration guide already reflects this and says withEventReplay() can be removed, but the hydration guide still presents it as required.

What is the new behavior?

The section now says that event replay is enabled by default with provideClientHydration(). It only shows withEventReplay() for apps that opt out of incremental hydration with withNoIncrementalHydration().

The redundant note about event replay being enabled automatically with incremental hydration is also removed.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Docs-only change in adev/src/content/guide/hydration.md.

@pullapprove
pullapprove Bot requested a review from crisbeto October 1, 2026 15:18
@angular-robot angular-robot Bot added the area: docs Related to the documentation label Oct 1, 2026
@ngbot ngbot Bot added this to the Backlog milestone Oct 1, 2026
Comment thread adev/src/content/guide/hydration.md Outdated
@GabeSilvaDev
GabeSilvaDev force-pushed the docs/hydration-event-replay-default branch from 97af885 to af8cb2f Compare October 1, 2026 17:23
@JeanMeche JeanMeche added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release labels Oct 1, 2026
JeanMeche
JeanMeche previously approved these changes Oct 1, 2026
@JeanMeche
JeanMeche self-requested a review October 1, 2026 17:47
@JeanMeche
JeanMeche dismissed their stale review October 1, 2026 17:47

Suggestion wasn't applied.

@JeanMeche
JeanMeche removed the request for review from crisbeto October 1, 2026 17:47
@JeanMeche JeanMeche removed the action: merge The PR is ready for merge by the caretaker label Oct 1, 2026
Since incremental hydration became the default in v22 and it enables
event replay, `provideClientHydration()` already replays events. The
hydration guide still told readers to enable event replay with
`withEventReplay()`; it now explains that it's on by default and when
`withEventReplay()` is still needed.
@GabeSilvaDev
GabeSilvaDev force-pushed the docs/hydration-event-replay-default branch from af8cb2f to 2a44346 Compare October 1, 2026 22:25
@GabeSilvaDev

Copy link
Copy Markdown
Contributor Author

Sorry about that, my previous push didn't actually include the change. Your suggestion is applied now in 2a44346.

@JeanMeche JeanMeche added the action: merge The PR is ready for merge by the caretaker label Oct 1, 2026
@kirjs
kirjs merged commit c5b4678 into angular:main Oct 2, 2026
24 checks passed
@kirjs

kirjs commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

This PR was merged into the repository. The changes were merged into the following branches:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

action: merge The PR is ready for merge by the caretaker area: docs Related to the documentation target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants