-
-
Notifications
You must be signed in to change notification settings - Fork 244
feat(eslint-plugin): add rule prefer-output-emitter-ref #2324
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
feat(eslint-plugin): add rule prefer-output-emitter-ref #2324
Conversation
View your CI Pipeline Execution ↗ for commit fd27147.
☁️ Nx Cloud last updated this comment at |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like a lot of overlap with @angular-eslint/prefer-output-readonly
?
🤦♂️ I forgot that |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2324 +/- ##
==========================================
+ Coverage 92.53% 92.56% +0.02%
==========================================
Files 184 186 +2
Lines 3726 3737 +11
Branches 836 836
==========================================
+ Hits 3448 3459 +11
Misses 215 215
Partials 63 63
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Thank you! |
Fixes #2258
This adds a new rule to the
eslint-plugin
calledprefer-output-emitter-ref
. There are two problems that this will detectIt will report a problem when an
@Output
decorator is used. This is not fixable since doing so would be quite complicated. There's also an Angular migration (feat(core): initial version of the output migration angular/angular#57604), so it's simpler to just use the migration.It will report a problem if an
OutputEmitterRef
property in a component or decorator is not read-only. This is fixable.