Skip to content
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(docs-infra): notify on data change inside OnPush component #55830

Conversation

pkozlowski-opensource
Copy link
Member

The SecondaryNavigation component was updating state outside of an event handler without notifying about this change. Modeling state as signal should take care of proper UI updates (note that I did just a mechanical change here, maybe there are better ways of dealing with this animations case).

@pkozlowski-opensource pkozlowski-opensource added action: review The PR is still awaiting reviews from at least one requested reviewer target: patch This PR is targeted for the next patch release area: adev Angular.dev documentation labels May 16, 2024
@ngbot ngbot bot modified the milestone: Backlog May 16, 2024
Copy link
Member

@JeanMeche JeanMeche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch

The SecondaryNavigation component was updating state outside of an event handler
without notifying about this change. Modeling state as signal should take
care of proper UI updates (note that I did just a mechanical change here, maybe
there are better ways of dealing with this animations case).
@JeanMeche JeanMeche added the action: merge The PR is ready for merge by the caretaker label May 17, 2024
@pkozlowski-opensource pkozlowski-opensource removed the action: review The PR is still awaiting reviews from at least one requested reviewer label May 17, 2024
dylhunn pushed a commit that referenced this pull request May 21, 2024
…55830)

The SecondaryNavigation component was updating state outside of an event handler
without notifying about this change. Modeling state as signal should take
care of proper UI updates (note that I did just a mechanical change here, maybe
there are better ways of dealing with this animations case).

PR Close #55830
@dylhunn dylhunn closed this in 831a20b May 21, 2024
@dylhunn
Copy link
Contributor

dylhunn commented May 21, 2024

This PR was merged into the repository by commit 831a20b.

dylhunn pushed a commit that referenced this pull request May 21, 2024
…55830)

The SecondaryNavigation component was updating state outside of an event handler
without notifying about this change. Modeling state as signal should take
care of proper UI updates (note that I did just a mechanical change here, maybe
there are better ways of dealing with this animations case).

PR Close #55830
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: adev Angular.dev 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.

None yet

3 participants