Closed timdeschryver closed 1 month ago
@timdeschryver if you ok with that, I can make it same way I made it there https://github.com/ngrx/platform/blob/main/projects/ngrx.io/content/guide/eslint-plugin/rules/prefer-protected-state.md
That would be awesome @paweltwardziak !
Ok @timdeschryver, on it
@timdeschryver Sorry for the delay, I've been a bit busy these past few days. Tomorrow I will raise my PR 👍
@timdeschryver see #4515 I've updated prefer-protected-state.md in that PR as well - I am not sure whether or not this is something acceptable to mix a little PR responibilities. Let me knwo - I can split it into two commits :)
@timdeschryver see #4515 I've updated prefer-protected-state.md in that PR as well - I am not sure whether or not this is something acceptable to mix a little PR responibilities. Let me knwo - I can split it into two commits :)
For this case it's fine. 😉
Information
The rule
signal-store-feature-should-use-generic-type
should be documented at https://github.com/ngrx/platform/blob/main/projects/ngrx.io/content/guide/eslint-plugin/rules/signal-store-feature-should-use-generic-type.md.It should also contain one or more examples showcasing some "bad" and "good" snippets. For some examples we can take a look at the test cases at https://github.com/ngrx/platform/blob/main/modules/eslint-plugin/spec/rules/signals/signal-store-feature-should-use-generic-type.spec.ts
Documentation page
https://ngrx.io/guide/eslint-plugin/rules/signal-store-feature-should-use-generic-type
I would be willing to submit a PR to fix this issue