Bug: onUnhandledError and onStoppedNotification are handled differently
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 31.7k
- Forks
- 3k
- PR merge metrics
- No merged PRs in 30d
Description
Decision from core team about direction to take is in this thread: https://github.com/ReactiveX/rxjs/pull/6436#issuecomment-1076799621
Basically, we shouldn't honor the handler being changed "after the fact".
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the core-team decision in the linked pull request comment, then trace the handling paths for onUnhandledError and onStoppedNotification. Compare how each observes handler changes after the notification is initiated; done means both follow the agreed rule of not honoring changes made after the fact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100