Conversation
Co-authored-by: patrickthornton <patrickthornton@users.noreply.github.com>
#12704) * ir polish * biome * release 3.85.3 * whoops * snap
bytes omit wire tests, v4.59.3
…12719) * parse x-fern-sdk-method-name on channel * snaps * release 3.86.0 * snaps 2
version bump
Co-authored-by: patrickthornton <patrickthornton@users.noreply.github.com>
…atching (#12717) * test(go-sdk): add exhaustive fixture case demonstrating bytes body with path params bug Co-Authored-By: unknown <> * fix(go): generate valid bytes.NewReader for bytes body dynamic snippets Co-Authored-By: unknown <> * test(go-sdk): update exhaustive fixture output after bytes body fix Co-Authored-By: unknown <> * fix(go): use associateByWireValueOrDefault for path parameters in dynamic snippets Co-Authored-By: unknown <> * chore(go): update changelog to include path parameter fix Co-Authored-By: unknown <> * fix(go): default WireMock stub response to empty JSON object for named response types When an endpoint example has a null/missing response body but the endpoint declares a JSON response with a named type (e.g., a struct), the WireMock stub now returns {} instead of "". This prevents JSON unmarshaling errors in strongly-typed languages like Go where a string cannot be deserialized into a struct. Co-Authored-By: unknown <> * test(go-sdk): add example with object response for bytes body endpoint in exhaustive fixture Co-Authored-By: unknown <> * test(go-sdk): update exhaustive fixture output after WireMock stub response fix Co-Authored-By: unknown <> * chore(go): update changelog to include WireMock stub response fix Co-Authored-By: unknown <> * test(go): update IR snapshot tests for exhaustive fixture Co-Authored-By: unknown <> * chore(seed): add exhaustive to allowedFailures for generators that don't support bytes Co-Authored-By: unknown <> * chore(seed): use specific config variants in allowedFailures for exhaustive fixture Co-Authored-By: unknown <> * fix(go): handle missing path parameters in wire test URL verification When an endpoint example has no path parameter values, the WireMock mapping has no pathParameters entry. buildBasePath now falls back to URL-encoded default values matching what associateByWireValueOrDefault synthesizes, ensuring VerifyRequestCount matches the actual client request URL. Co-Authored-By: unknown <> --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )