-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
"rxjs-no-unsafe-scope" false positve #101
Comments
See #56 |
Regarding #56, I don't plan on prioritising that issue at all. I have other projects - that will be more beneficial for RxJS developers - that need my time. I can add You might want to take that into consideration when weighing up whether or not you want - or even really need - this rule. |
@cartant Okay, i get you. So, is it fair to say that this project will phase out (perhaps, in favor of eslint or something else)? |
This project will be around for the foreseeable future, but perhaps not this rule. If it continues to effect bugs, I will likely deprecate and delete it. There are other, more useful, rules in this package than the unsafe scope rule. |
Gotcha. Thanks for the explanation. |
"rxjs-no-unsafe-scope" produces a false positive for the following piece of code:
What is interesting to note is that "bootstrapModule" returns a Promise, not Observable. So, i do not expect "rxjs-tslint-rules" to kick in here at all.
The text was updated successfully, but these errors were encountered: