gRPC-based APIs use an empty string as a "no page token", whereas REST-based APIs
use a null reference instead. The value here will be consistent with the value returned
by the API itself.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThe \u003ccode\u003ePage<TResource>\u003c/code\u003e class represents a page of resources, ensuring that fewer results are returned only if no more data is available to fetch.\u003c/p\u003e\n"],["\u003cp\u003eThis class implements \u003ccode\u003eIEnumerable<TResource>\u003c/code\u003e and \u003ccode\u003eIEnumerable\u003c/code\u003e, allowing iteration over the resources within the page.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ePage<TResource>\u003c/code\u003e class includes a constructor that takes an \u003ccode\u003eIEnumerable<TResource>\u003c/code\u003e for resources and a string for the \u003ccode\u003enextPageToken\u003c/code\u003e, facilitating the creation of a page from a resource sequence.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eNextPageToken\u003c/code\u003e property provides a string to retrieve the next page of resources, with a notable difference in how gRPC (empty string) and REST (null reference) APIs handle the absence of a token.\u003c/p\u003e\n"],["\u003cp\u003eThe page class has methods GetEnumerator() to make it easy to get the resources within the page.\u003c/p\u003e\n"]]],[],null,[]]
