Skip to content

fix: Path params are ordered based on the path template, not endpoint definition #687

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

Merged
merged 5 commits into from
Apr 14, 2025

Conversation

bmoylan
Copy link
Contributor

@bmoylan bmoylan commented Mar 28, 2025

Previously, astForEndpointMethodBodyRequestParams would create the httpclient.WithPathf parameter using the argument ordering present in the conjure definition/intermediate representation. This is incorrect. Instead, the path parameters must match their ordering in the endpoint's http path template.

We are NOT changing the argument ordering in the generated go interfaces, since it would be a (potentially silent) break and arguments are referenced by name, not position.


This change is Reviewable

@bulldozer-bot bulldozer-bot bot merged commit 9c7cada into develop Apr 14, 2025
9 checks passed
@bulldozer-bot bulldozer-bot bot deleted the bm/path-param-order branch April 14, 2025 20:02
@autorelease3
Copy link

autorelease3 bot commented Apr 14, 2025

Released v6.66.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants