docs: clarify range single argument behavior - #7607
Open
MakenRosa wants to merge 1 commit into
Open
Conversation
MakenRosa
force-pushed
the
docs-rxjs-range-count
branch
from
August 3, 2026 01:19
97e7cbe to
d86a254
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Clarifies the
rangeJSDoc so the generated API documentation explains that a single argument is treated ascount, notstart.Also removes the misleading
finite rangewording becauserange(start, Infinity)can emit an unbounded sequence when downstream unsubscription stops it.Validation
7.xversiongit diff --checkFixes #5721