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
Implement Pager resumption even through into_pages (#3286)
By design, we didn't support resuming `Pager` (`ItemIterator`) but, upon
further discussion, decided we can but will resume from the current page
until all items on the current page are processed.
This also fixes a problem that, because of the design, we didn't pass
through resumption to the `PageIterator` at all - it couldn't even
resume as a `PageIterator` for subsequent pages.
Copy file name to clipboardExpand all lines: sdk/core/azure_core/CHANGELOG.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,7 @@
4
4
5
5
### Features Added
6
6
7
+
- Added `ItemIterator::continuation_token()` and `with_continuation_token()` to resume paging items. The current page is restarted until _after_ all items have been iterated.
7
8
- Added `Response::to_raw_response()` function to create a `RawResponse` from cloned data.
8
9
- Added `UrlExt::append_path()`.
9
10
- Implemented `IntoFuture` for a `Poller`. Call `await` on a Poller to get the final model, or `into_stream()` to get a `futures::Stream` to poll the operation manually.
@@ -27,6 +28,8 @@
27
28
28
29
### Bugs Fixed
29
30
31
+
-`ItemIterator::into_pages()` now properly supports resuming from the current page until _after_ all items have been iterated.
0 commit comments