Add Nullable annotations in ListExtractor#1313
Merged
TobiGr merged 1 commit intoTeamNewPipe:devfrom Jul 7, 2025
Merged
Conversation
AudricV
changed the title
AudricV
changed the title
ShareASmile
added
the
code quality
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
3 participants
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
This PR marks the
nextPagefield inInfoItemsPage<T>andListExtractor<T>as@Nullable.This improves compatibility with Kotlin consumers like the NewPipe app.
Motivation
Without this annotation, Kotlin treats
nextPageas non-null, which may lead to incorrect assumptions when no further page exists.Notes
./gradlew test) and failures are due to unrelated issues (e.g., YouTube JS changes, geo-restrictions).Related Issue
Fixes #1312