Skip to content

Fix OpenApiEncoding explode property serialization#2508

Merged
baywet merged 1 commit into
microsoft:support/v1from
kammerjaeger:fix/explode-default-value
Sep 19, 2025
Merged

Fix OpenApiEncoding explode property serialization#2508
baywet merged 1 commit into
microsoft:support/v1from
kammerjaeger:fix/explode-default-value

Conversation

@kammerjaeger

Copy link
Copy Markdown
Contributor

Fix: Explode serialization is wrong when style is "form"

This fixes the same problem as #544 but for OpenApiEncoding.
The spec describes different behavior depending on if it is set or not (see: https://spec.openapis.org/oas/v3.1.0.html#fixed-fields-12) and also different defaults depending on the style value.
This also needs to be cherry picked to main, I just need it for v1 but will create a pr to main with the change if this pr is fine.

Please let me know what you think.

@kammerjaeger kammerjaeger requested a review from a team as a code owner September 18, 2025 21:13
@kammerjaeger kammerjaeger force-pushed the fix/explode-default-value branch from f6c558d to c14dd24 Compare September 18, 2025 21:39

@baywet baywet left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution!

@baywet

baywet commented Sep 19, 2025

Copy link
Copy Markdown
Member

@kammerjaeger can you please also sign the CLA? (see the bot comment)

@baywet baywet enabled auto-merge September 19, 2025 12:43
@kammerjaeger

Copy link
Copy Markdown
Contributor Author

@microsoft-github-policy-service agree company="AMD"

@baywet baywet merged commit 09b5a28 into microsoft:support/v1 Sep 19, 2025
8 checks passed
@kammerjaeger kammerjaeger deleted the fix/explode-default-value branch September 19, 2025 20:26
@kammerjaeger

Copy link
Copy Markdown
Contributor Author

Thanks for the fast review. How often do you release new versions?

@baywet

baywet commented Sep 19, 2025

Copy link
Copy Markdown
Member

We make releases as needed, as long as it's possible because this is a maintenance branch.
This process is supposed to be automated, but for some reason it got stuck because we already have a mainline release???
https://github.com/microsoft/OpenAPI.NET/actions/runs/17869041888/job/50818331357

Once we release main, I'll re-run it manually, please ping me if I forget :)

@baywet

baywet commented Sep 20, 2025

Copy link
Copy Markdown
Member

@kammerjaeger I had to trigger the release manually to circumvent the the issue, I'm waiting for somebody to approve it #2513

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants