-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue #3937: Paged flux draft PR #4045
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JonathanGiles
requested changes
Jun 26, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks good. Focus on tests and docs now.
JonathanGiles
approved these changes
Jun 27, 2019
core/azure-core/pom.xml
Outdated
<scope>provided</scope> | ||
</dependency> | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One too many newlines.
JonathanGiles
approved these changes
Jun 27, 2019
alzimmermsft
approved these changes
Jun 28, 2019
sima-zhu
pushed a commit
that referenced
this pull request
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
sima-zhu
pushed a commit
to sima-zhu/azure-sdk-for-java
that referenced
this pull request
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Draft prototype of paged flux to get some early feedback on the general direction of this implementation.
I have also updated
ConfigurationAsyncClient
implementation forlistSettings
to return a paged flux to verify that all existing tests are passing using the item flux. After addressing all review feedback, I will add tests toConfigurationAsyncClient
to test subscription by page.Logs from
PagedFluxTest
: