deprecation warning when using of as intended
See original GitHub issueBug Report
Current Behavior
I’ve got the tslint rule "deprecation": true enabled and it is now throwing warnings when using of without a scheduler.
Reproduction
import { of } from "rxjs"
of(4) // of is deprecated: use {@link scheduled} instead `scheduled([a, b, c], scheduler)` (deprecation)
Expected behavior No warning
Environment
- Runtime: Node v11.13.0
- RxJS version: 6.5.1
- tslint version 5.16.0
Issue Analytics
- State:
- Created 4 years ago
- Reactions:63
- Comments:16 (3 by maintainers)
Top Results From Across the Web
python - Difference between DeprecationWarning ...
As I understand these, DeprecationWarning means "change your code now or it will break soon", PendingDeprecationWarning means "you're going to ...
Read more >warnings — Warning control — Python 3.11.1 documentation
DeprecationWarning. Base category for warnings about deprecated features when those warnings are intended for other Python developers (ignored by default, ...
Read more >Deprecation — sktime documentation
To deprecate tags, it needs to be ensured that warnings are raised when the tag is used. There are two common scenarios: removing...
Read more >Who should see Python deprecation warnings? - LWN.net
The first line filters out DeprecationWarning events, such as the warnings regarding await and async in the 3.6 release. Those warnings were also...
Read more >Python deprecation - DEV Community
To warn about deprecation, you need to set Python's builtin DeprecationWarning as category. To let the warning refer to the caller, so you...
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

Well, I might sound like a dick here. But … it’s a minor bug, that what fixed immediately after it’s been spotted by (at least) hundreds ppl. 2 weeks passes and it’s not released. I know, I know. Just a bit frustrating.
@cartant I can do it