You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to offer improved pagination APIs. At present our pagination is transparent - users simply receive a Flux, and we transparently unroll the paged responses and put them into a Flux stream.
Rather than this, we should consider introducing a PagedFlux type. By default (as shown in the repo link above), the user will still be able to work with the common case of Flux, but by calling byPage(), the user will be able to get a Flux<PagedResponse<T>> and iterate per page, rather than per item.
The text was updated successfully, but these errors were encountered:
* Initial prototype for paged flux
* Update unit tests and javadocs
* Remove unused imports
* Updated to use paged response instead of continuation token
* Update javadocs
* Supplier and function
* Update javadocs, add code snippets and more unit tests
* Undo package-info changes
* Undo package-info changes
* Update javadocs
* Add jsr dependency
* Remove extra blank line
* Initial prototype for paged flux
* Update unit tests and javadocs
* Remove unused imports
* Updated to use paged response instead of continuation token
* Update javadocs
* Supplier and function
* Update javadocs, add code snippets and more unit tests
* Undo package-info changes
* Undo package-info changes
* Update javadocs
* Add jsr dependency
* Remove extra blank line
sima-zhu
pushed a commit
to sima-zhu/azure-sdk-for-java
that referenced
this issue
Jun 29, 2019
* Initial prototype for paged flux
* Update unit tests and javadocs
* Remove unused imports
* Updated to use paged response instead of continuation token
* Update javadocs
* Supplier and function
* Update javadocs, add code snippets and more unit tests
* Undo package-info changes
* Undo package-info changes
* Update javadocs
* Add jsr dependency
* Remove extra blank line
Refer to the exploratory changes in my repo.
We need to offer improved pagination APIs. At present our pagination is transparent - users simply receive a Flux, and we transparently unroll the paged responses and put them into a Flux stream.
Rather than this, we should consider introducing a
PagedFlux
type. By default (as shown in the repo link above), the user will still be able to work with the common case of Flux, but by callingbyPage()
, the user will be able to get aFlux<PagedResponse<T>>
and iterate per page, rather than per item.The text was updated successfully, but these errors were encountered: