Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

No-unsafe-first not working as expected

See original GitHub issue

The 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 GitHub Comments

2reactions

cartantcommented, Dec 3, 2019

It’s a bug - the regular expression needs a trailing $ to avoid matching in the middle of an identifier.

1reaction

cartantcommented, Dec 3, 2019

Fixed in 0.0.2-beta.12. Thanks for reporting it, @hnipps

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 ...