The hasNext description currently says that nextPageToken will always be supplied.
If we decide that nextPageToken should only be present when hasNext=true, this description should be updated accordingly. Otherwise, the spec should clarify what value nextPageToken has when hasNext=false.
Making nextPageToken optional when hasNext is false would simplify client-side logic, as consumers wouldn't need to handle 'empty' or 'dummy' tokens for terminal pages.
Originally posted by @Mehrn0ush in #231 (comment)
The
hasNextdescription currently says thatnextPageTokenwill always be supplied.If we decide that
nextPageTokenshould only be present whenhasNext=true, this description should be updated accordingly. Otherwise, the spec should clarify what valuenextPageTokenhas whenhasNext=false.Making nextPageToken optional when hasNext is false would simplify client-side logic, as consumers wouldn't need to handle 'empty' or 'dummy' tokens for terminal pages.
Originally posted by @Mehrn0ush in #231 (comment)