Skip to content

fix(Subscriber): next method no longer has optional value argument#7290

Merged
benlesh merged 1 commit intoReactiveX:masterfrom
benlesh:fix/Subscriber-next-type
Jun 19, 2023
Merged

fix(Subscriber): next method no longer has optional value argument#7290
benlesh merged 1 commit intoReactiveX:masterfrom
benlesh:fix/Subscriber-next-type

Conversation

@benlesh
Copy link
Member

@benlesh benlesh commented Jun 19, 2023

Resolves #2852
Related #7172

@benlesh benlesh force-pushed the fix/Subscriber-next-type branch from 59162c7 to 7518b09 Compare June 19, 2023 16:15
@benlesh benlesh merged commit 1c5673f into ReactiveX:master Jun 19, 2023
@josepot
Copy link
Contributor

josepot commented Oct 26, 2023

I just faced a nasty runtime error that could have been avoided if this fix had already been shipped. I'd like to know: will there be a release patch containing this fix? Or will it be treated as a "breaking change," meaning we'll need to wait for version 8?

FWIW, I strongly believe this deserves a patch release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Subject.prototype.next() should only accept T, not T | undefined

3 participants