Should the "effects and epics" rules from the main RxJS plugin be split out?

[JasonWeinzierl]

This plugin has some rules that are only relevant when using NgRx or redux-observable. redux-observable has since switched to maintenance mode, and NgRx is Angular-specific.

In my opinion, those rules are only relevant in the context of Angular, they add confusion about what rules are helpful for all RxJS users versus what are library-specific, and they don't belong in the main plugin.

There are a few options here:

1. Leave the "effects and epics" rules as-is. They have existed in this plugin since the beginning. However as mentioned, they may not belong here and may incur maintenance cost & confusion.
2. Move the rules into the newly forked eslint-plugin-rxjs-angular-x plugin: https://github.com/JasonWeinzierl/eslint-plugin-rxjs-angular-x . I've started that fork for the same reasons as this one, and so it may start to grow into a larger hub for Angular-specific rules and configurations.
3. See if NgRx would like to take the rules into their own plugin: https://www.npmjs.com/package/@ngrx/eslint-plugin . One of NgRx's rules is already based on rxjs/no-cyclic-action (https://ngrx.io/guide/eslint-plugin/rules/avoid-cyclic-effects), so they might be willing to take on the other NgRx-specific rules. This would leave redux-observable owners behind, but, as mentioned, that library might be falling out of use anyways.
   • Discussion opened on the NgRx repository here: Take ownership of NgRx-specific rules in ESLint plugin for RxJS? ngrx/platform#4689