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.
Allow rxjs-no-patched to have exclusions?
See original GitHub issueHi there, amazing work on these rules first of all!
Is it possible to allow the rxjs-no-patched rule to have exclusions to the rule? My use case is on Observable.of, Observable.never, and the rest that are in rxjs/add/observable that I want to exclude out of the rule — having functions like never() and throw() in the codebase can be confusing and we disallow renaming imports from another lint rule already.
I’m thinking of the same syntax as rxjs-add’s file or a list of the patched methods to disallow. Let me know what you think.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sounds reasonable. I’ll add it when I next have 15 or so minutes to spare.
That was fast, cheers!
Another thing you might wanna consider is having the same option setup in
rxjs-no-add. Sincerxjs/add/observableis going to be used in one patch import file, it might be necessary to exclude observable patching too.