API documentation for discoveryengine_v1beta.services.conversational_search_service.pagers module.
Classes
ListConversationsAsyncPager
ListConversationsAsyncPager(
method: typing.Callable[
[...],
typing.Awaitable[
google.cloud.discoveryengine_v1beta.types.conversational_search_service.ListConversationsResponse
],
],
request: google.cloud.discoveryengine_v1beta.types.conversational_search_service.ListConversationsRequest,
response: google.cloud.discoveryengine_v1beta.types.conversational_search_service.ListConversationsResponse,
*,
metadata: typing.Sequence[typing.Tuple[str, str]] = ()
)A pager for iterating through list_conversations requests.
This class thinly wraps an initial
ListConversationsResponse object, and
provides an __aiter__ method to iterate through its
conversations field.
If there are more pages, the __aiter__ method will make additional
ListConversations requests and continue to iterate
through the conversations field on the
corresponding responses.
All the usual ListConversationsResponse attributes are available on the pager. If multiple requests are made, only the most recent response is retained, and thus used for attribute lookup.
ListConversationsPager
ListConversationsPager(
method: typing.Callable[
[...],
google.cloud.discoveryengine_v1beta.types.conversational_search_service.ListConversationsResponse,
],
request: google.cloud.discoveryengine_v1beta.types.conversational_search_service.ListConversationsRequest,
response: google.cloud.discoveryengine_v1beta.types.conversational_search_service.ListConversationsResponse,
*,
metadata: typing.Sequence[typing.Tuple[str, str]] = ()
)A pager for iterating through list_conversations requests.
This class thinly wraps an initial
ListConversationsResponse object, and
provides an __iter__ method to iterate through its
conversations field.
If there are more pages, the __iter__ method will make additional
ListConversations requests and continue to iterate
through the conversations field on the
corresponding responses.
All the usual ListConversationsResponse attributes are available on the pager. If multiple requests are made, only the most recent response is retained, and thus used for attribute lookup.