[prefer-readonly-signals] New rule for checking that signals are defined as readonly #1719
Labels
package: eslint-plugin
Angular-specific TypeScript rules
triage
This issue needs to be looked at and categorized by a maintainer
Description and reproduction of the issue
The new Angular signals should only be updated using the
.set()
or.update()
function, never overwritten.For this reason I propose a new rule which checks that all signals are marked as readonly.
Incorrect examples
Correct examples
The text was updated successfully, but these errors were encountered: