Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix(core): allow signal write error #57973

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

Closed

Conversation

cexbrayat
Copy link
Member

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.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Now that effects allow to write to signals (see 4e890cc), the SIGNAL_WRITE_FROM_ILLEGAL_CONTEXT error is only thrown in computed functions.

What is the new behavior?

This commit updates the error message to remove the mention of effects and of the deprecated allowSignalWrites option.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Now that effects allow to write to signals (see angular@4e890cc),
the SIGNAL_WRITE_FROM_ILLEGAL_CONTEXT error is only thrown in `computed` functions.
This commit updates the error message to remove the mention of effects and of the deprecated `allowSignalWrites` option.
@pullapprove pullapprove bot requested a review from AndrewKushnir September 26, 2024 11:39
@angular-robot angular-robot bot added the area: core Issues related to the framework runtime label Sep 26, 2024
@ngbot ngbot bot added this to the Backlog milestone Sep 26, 2024
@AndrewKushnir AndrewKushnir requested review from alxhub and removed request for AndrewKushnir September 26, 2024 15:09
@AndrewKushnir AndrewKushnir added target: patch This PR is targeted for the next patch release action: review The PR is still awaiting reviews from at least one requested reviewer labels Sep 26, 2024
@pkozlowski-opensource pkozlowski-opensource added action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release and removed 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 labels Oct 3, 2024
@pkozlowski-opensource pkozlowski-opensource removed the request for review from alxhub October 3, 2024 17:25
@devversion
Copy link
Member

This PR was merged into the repository by commit ee426c6.

The changes were merged into the following branches: main

@devversion devversion closed this in ee426c6 Oct 4, 2024
@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 4, 2024
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: core Issues related to the framework runtime target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants