Skip to content

fix(platform-server): align server renderer interface with base renderer#47868

Closed
crisbeto wants to merge 1 commit intoangular:mainfrom
crisbeto:47844/server-renderer-align
Closed

fix(platform-server): align server renderer interface with base renderer#47868
crisbeto wants to merge 1 commit intoangular:mainfrom
crisbeto:47844/server-renderer-align

Conversation

@crisbeto
Copy link
Member

The ServerRenderer wasn't aligned with the Renderer2 interface which meant that it was still referring to the old debugInfo parameters. It also wasn't implementing the preserveContent argument of selectRootElement which can lead to incosistencies between the server and the client.

Fixes #47844.

The `ServerRenderer` wasn't aligned with the `Renderer2` interface which meant that it was still referring to the old `debugInfo` parameters. It also wasn't implementing the `preserveContent` argument of `selectRootElement` which can lead to incosistencies between the server and the client.

Fixes angular#47844.
@crisbeto crisbeto added action: review The PR is still awaiting reviews from at least one requested reviewer area: server Issues related to server-side rendering target: rc This PR is targeted for the next release-candidate labels Oct 25, 2022
@ngbot ngbot bot added this to the Backlog milestone Oct 25, 2022
@crisbeto crisbeto marked this pull request as ready for review October 25, 2022 07:59
@pullapprove pullapprove bot requested a review from dylhunn October 25, 2022 07:59
@alan-agius4 alan-agius4 removed the request for review from dylhunn October 25, 2022 09:04
@crisbeto crisbeto added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Oct 25, 2022
@pkozlowski-opensource
Copy link
Member

@alan-agius4 @crisbeto is there any test we could put in place to prevent this type of de-synchronisation happening in the future?

@crisbeto
Copy link
Member Author

I think that normally this would've been caught by TS through the Renderer2 interface. This time it wasn't, because the old debugInfo parameter was typed as any.

@pkozlowski-opensource
Copy link
Member

This PR was merged into the repository by commit 54e32da.

pkozlowski-opensource pushed a commit that referenced this pull request Oct 25, 2022
…rer (#47868)

The `ServerRenderer` wasn't aligned with the `Renderer2` interface which meant that it was still referring to the old `debugInfo` parameters. It also wasn't implementing the `preserveContent` argument of `selectRootElement` which can lead to incosistencies between the server and the client.

Fixes #47844.

PR Close #47868
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Nov 25, 2022
trekladyone pushed a commit to trekladyone/angular that referenced this pull request Feb 1, 2023
…rer (angular#47868)

The `ServerRenderer` wasn't aligned with the `Renderer2` interface which meant that it was still referring to the old `debugInfo` parameters. It also wasn't implementing the `preserveContent` argument of `selectRootElement` which can lead to incosistencies between the server and the client.

Fixes angular#47844.

PR Close angular#47868
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: server Issues related to server-side rendering target: rc This PR is targeted for the next release-candidate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DefaultServerRenderer2 does not correctly implement selectRootElement

3 participants