-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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 preferProtectedState rule #4488
Conversation
✅ Deploy Preview for ngrx-io canceled.Built without sensitive environment variables
|
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.
Well done @NgDaddy. I've just left a few potential textual improvements.
What we should discuss, if it should be fixable and if it should be of type 'problem'.
...ects/ngrx.io/content/guide/eslint-plugin/rules/signal-store-should-prefer-protected-state.md
Outdated
Show resolved
Hide resolved
...ects/ngrx.io/content/guide/eslint-plugin/rules/signal-store-should-prefer-protected-state.md
Outdated
Show resolved
Hide resolved
modules/eslint-plugin/src/rules/signals/signal-store-should-prefer-protected-state.ts
Outdated
Show resolved
Hide resolved
modules/eslint-plugin/src/rules/signals/signal-store-should-prefer-protected-state.ts
Outdated
Show resolved
Hide resolved
modules/eslint-plugin/src/rules/signals/signal-store-should-prefer-protected-state.ts
Outdated
Show resolved
Hide resolved
modules/eslint-plugin/src/rules/signals/signal-store-should-prefer-protected-state.ts
Outdated
Show resolved
Hide resolved
modules/eslint-plugin/spec/rules/signals/signal-store-should-prefer-protected-state.spec.ts
Outdated
Show resolved
Hide resolved
Many thanks @rainerhahnekamp for the valuable CR 👍 |
@rainerhahnekamp @timdeschryver converted to |
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.
Just left a comment on the messages. Tried it out already out in my project and confirm it works.
modules/eslint-plugin/src/rules/signals/signal-store-should-prefer-protected-state.ts
Outdated
Show resolved
Hide resolved
modules/eslint-plugin/src/rules/signals/signal-store-should-prefer-protected-state.ts
Outdated
Show resolved
Hide resolved
Co-authored-by: Rainer Hahnekamp <rainer.hahnekamp@gmail.com>
Co-authored-by: Rainer Hahnekamp <rainer.hahnekamp@gmail.com>
@rainerhahnekamp nice catch, the messages are better now, applied :) ready to review again |
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.
I have also tested it manually. Good stuff @NgDaddy
thanks @rainerhahnekamp 👍 I am open for another task if you have any :) |
@timdeschryver ready to CR again :) |
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.
Thanks for your work on this @NgDaddy
I think the overall structure is good, I just left a few comments on details.
modules/eslint-plugin/src/rules/signals/signal-store-should-prefer-protected-state.ts
Outdated
Show resolved
Hide resolved
modules/eslint-plugin/spec/rules/signals/signal-store-should-prefer-protected-state.spec.ts
Outdated
Show resolved
Hide resolved
...ects/ngrx.io/content/guide/eslint-plugin/rules/signal-store-should-prefer-protected-state.md
Outdated
Show resolved
Hide resolved
… rule to preferProtectedState
@rainerhahnekamp @timdeschryver all suggestions have been applied. Ready to CR. |
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.
Nice work, thanks @NgDaddy
The build should be resolved with #4492, then we can merge this in 😎
At your service guys, my pleasure 😃 I am looking forward to having another opportunity to do something for @ngrx 😎 |
I've just pushed small refactor 2e45c0e - standardize of namings |
Thanks @NgDaddy! |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
#4474
What is the current behavior?
See #4474
Closes #4474
What is the new behavior?
See #4474
Does this PR introduce a breaking change?
Other information