-
Notifications
You must be signed in to change notification settings - Fork 0
release: 0.10.0 #184
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
Closed
stainless-app
wants to merge
49
commits into
main
from
release-please--branches--main--changes--next
Closed
release: 0.10.0 #184
stainless-app
wants to merge
49
commits into
main
from
release-please--branches--main--changes--next
Conversation
This file contains hidden or 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
3aba691 to
fc25618
Compare
f141119 to
fc13394
Compare
bee2017 to
7c8e53c
Compare
55acb62 to
96fdae2
Compare
1ffcfb2 to
decbdbc
Compare
267aa78 to
decbdbc
Compare
refactor(client)!: refactor async auto-pagination
refactor(client)!: rename `getNextPage{,Params}` to `nextPage{,Params}`
refactor(client)!: swap `nextPage{,Params}` to return non-optional
# Migration
- If you were referencing the `AutoPager` class on a specific `*Page` or `*PageAsync` type, then you should instead reference the shared `AutoPager` and `AutoPagerAsync` types, under the `core` package
- `AutoPagerAsync` now has different usage. You can call `.subscribe(...)` on the returned object instead to get called back each page item. You can also call `onCompleteFuture()` to get a future that completes when all items have been processed. Finally, you can call `.close()` on the returned object to stop auto-paginating early
- If you were referencing `getNextPage` or `getNextPageParams`:
- Swap to `nextPage()` and `nextPageParams()`
- Note that these both now return non-optional types (use `hasNextPage()` before calling these, since they will throw if it's impossible to get another page)
There are examples and further information about pagination in the readme.
2ad84cd to
e9248c0
Compare
00b8b44 to
f8dd702
Compare
0dab993 to
5d19342
Compare
Refactor `HttpRequest` to always take a `baseUrl`, instead of storing this in `OkHttpClient`. This allows better reuse of `OkHttpClient` when changing the `baseUrl`.
fa210fd to
729a979
Compare
52028bd to
0fd4355
Compare
cba6c1a to
3e67a54
Compare
72364ac to
ce8a40c
Compare
8007685 to
76e5e15
Compare
09a45da to
5904a7a
Compare
28e63b5 to
ab5aa6c
Compare
264fdb6 to
00333f4
Compare
e7b7ee2 to
dba7eae
Compare
eafa84f to
b73560b
Compare
d7b0212 to
e235503
Compare
e235503 to
526bf4b
Compare
526bf4b to
5b69fb5
Compare
Running the formatter through Spotless is slow because Spotless synchronously runs the formatter on each file. Running the formatter directly parallelizes the formatting across cores.
5b69fb5 to
7c77c5a
Compare
7c77c5a to
e6c1788
Compare
e6c1788 to
56054ee
Compare
56054ee to
2f5f705
Compare
2f5f705 to
e591de1
Compare
e591de1 to
11016c4
Compare
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.
Automated Release PR
0.10.0 (2025-08-22)
Full Changelog: v0.9.0...v0.10.0
⚠ BREAKING CHANGES
AutoPagerclass on a specific*Pageor*PageAsynctype, then you should instead reference the sharedAutoPagerandAutoPagerAsynctypes, under thecorepackageAutoPagerAsyncnow has different usage. You can call.subscribe(...)on the returned object instead to get called back each page item. You can also callonCompleteFuture()to get a future that completes when all items have been processed. Finally, you can call.close()on the returned object to stop auto-paginating earlygetNextPageorgetNextPageParams:nextPage()andnextPageParams()hasNextPage()before calling these, since they will throw if it's impossible to get another page)Features
{QueryParams,Headers}#put(String, JsonValue)methods (2ed0bd5)withOptionsmethod (0fd4355)Bug Fixes
withOptionsusage when original is gc'd (c17580b)@MustBeClosedfor future returning methods (5d19342)Performance Improvements
Chores
actions/setup-javato v4 (3769b89)-Xbackend-threads=0option (96fdae2)[...]in[@see](https://github.com/see)(a0ef543)Documentation
Refactors
ClientOptionsTestchange (2e7263e)This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions