docs(sdks): document Go enableRequestBodyPagination option - #6652
Merged
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Contributor
|
🌿 Preview your docs: https://fern-preview-devin-1786813681-go-request-body-pagination.docs.buildwithfern.com/learn Here are the markdown pages you've updated: |
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
…avior Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
devalog
approved these changes
Aug 17, 2026
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
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.
Summary
Go SDKs silently skipped auto-pagination when an endpoint's cursor or offset page property lives in the request body instead of a query parameter, so those APIs generated a plain single-response method and users had to hand-roll the paging loop. The Go generator now supports request-body cursor and offset pagination behind the new
enableRequestBodyPaginationoption, bringing Go in line with the other languages. The option is off by default because turning it on changes affected methods' return types (from a response to a pager), keeping existing generated signatures stable until customers opt in.Implements docs for: feat(go): opt-in auto-pagination for request body cursors and offsets (fern-api/fern#17352)
Pages changed
fern/products/sdks/generators/go/configuration.mdx— newenableRequestBodyPagination<ParamField>(boolean, defaultfalse) covering what it enables, why it is off by default, and that nested body page properties (cursor: $request.pagination.cursor) remain unsupported and still generate a plain method. Links to the auto-pagination deep dive.fern/products/sdks/deep-dives/configure-auto-pagination.mdx— the "Generated SDK behavior" tabs only had TypeScript and Python, so a Go-only sentence had nowhere natural to live. Added Go, Java, and C# tabs, and folded theenableRequestBodyPaginationrequirement into the Go tab. Each snippet matches the pager API in the generated SDKs:*core.Page[T]withIterator()/GetNextPage(ctx)(Go),SyncPagingIterable<T>with iteration,streamItems(), andnextPage()(Java),Pager<T>as anIAsyncEnumerable<T>consumed withawait foreach(C#).No SDK changelog entry added (generated automatically for the generators). Vale and
fern check --warningspass with no new findings.Link to Devin session: https://app.devin.ai/sessions/fbc018f9c6694760843c05d716902c69