[SDK-3990] Fix PaginatedResult.next() behaviour when no next page
#1543
Conversation
This file contains 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
github-actions
bot
temporarily deployed
to
staging/pull/1543/features
github-actions
bot
temporarily deployed
to
staging/pull/1543/bundle-report
github-actions
bot
temporarily deployed
to
staging/pull/1543/typedoc
lawrence-forooghian
changed the title
PaginatedResult.next() behaviour when no next pagePaginatedResult.next() behaviour when no next page
It is meant to return `null` (per TG4 and our documentation comments), but was returning `undefined`. Resolves #1542.
lawrence-forooghian
force-pushed
the
1542-next-page-not-null
branch
from
b3df0a4 to
8bd1706
Compare
owenpearson
approved these changes
Dec 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It's meant to return
null, notundefined. See commit messages for more details.Resolves #1542.