No-unsafe-first not working as expected
See original GitHub issueThe no-unsafe-first
rule doesn’t seem to work as expected.
I’m seeing ESLint errors when I use take(1)
inside an Angular component but no error when I use it inside an epic.
I’d expect to see the opposite: an error in the epic and no error in the component.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
redux-observable/redux-observable - Gitter
i m facing this problem. Type '(action$: Observable<any>) => Observable<{ type: string; payload: Object; }>' has no properties in common with type ...
Read more >rxjs-tslint-rules | Yarn - Package Manager
This can cause problems, as whether or not Observable is patched then depends upon ... rxjs-no-unsafe-first, Disallows unsafe first and take usage in...
Read more >cartant/rxjs-tslint-rules release history - changelogs.md
Recent releases and changes to cartant/rxjs-tslint-rules.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It’s a bug - the regular expression needs a trailing
$
to avoid matching in the middle of an identifier.Fixed in
0.0.2-beta.12
. Thanks for reporting it, @hnipps