-
-
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
ng-add should also work for ESLint 9 flat config files #4643
Comments
@timdeschryver is it open for picking? I am willing to dive deep into the flat config. |
@pawel-twardziak feel free to tackle this issue. |
Ok @timdeschryver, I am on it, thanks |
@timdeschryver sorry for the delay, the begining of the year was packed with vacation days. I am back on it. |
No problem @pawel-twardziak , I hope you enjoyed your vacation. |
Hello, I noticed this issue has been in progress for some time. If it's okay, I would be happy to take over :) |
Feel free to take over :)
sob., 8 lut 2025, 20:12 użytkownik ALMOUNAYAR Adam ***@***.***>
napisał:
… Hello, I noticed this issue has been in progress for some time. If it's
okay, I would be happy to take over :)
—
Reply to this email directly, view it on GitHub
<#4643 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BLDYJ3DPAZ4QR47T5SRZ4TL2OZJJDAVCNFSM6AAAAABUERENLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBVHEYDONZZHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Which @ngrx/* package(s) are relevant/related to the feature request?
eslint-plugin
Information
Currently the NgRx eslint plugin only configures the NgRx plugin within a json file.
We should also add the option to configure our plugin within flat config files.
The schematic should automatically detect which file needs to be updated.
We can take a look at the Angular ESlint plugin for inspiration https://github.com/angular-eslint/angular-eslint/blob/390df5a211f7016be1bcc12c4e139796c1867867/packages/schematics/src/ng-add/index.ts#L41
Describe any alternatives/workarounds you're currently using
No response
I would be willing to submit a PR to fix this issue
The text was updated successfully, but these errors were encountered: