Skip to content
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

fix(openapi): Yaml openapi export should have numeric keys as string #6436

Conversation

DartCZ
Copy link
Contributor

@DartCZ DartCZ commented Jun 26, 2024

Description

The OpenAPI specification mandates that all keys in the Responses Object be strings, as outlined here: https://github.com/OAI/OpenAPI-Specification/blob/157a4c81ae537ef793b2bee368bc00d88b461de8/versions/3.0.2.md#patterned-fields-1.

This requirement includes values like '200', which PHP typecasts to integers. Therefore, Yaml should also adhere to this rule.

@DartCZ DartCZ changed the title fix(openapi-export): Yaml openapi export should have numeric keys as string fix(openapi): Yaml openapi export should have numeric keys as string Jun 26, 2024
@DartCZ DartCZ force-pushed the fix/openapi-export-yaml-should-numeric-key-as-string branch 3 times, most recently from d46a59f to 4324754 Compare June 26, 2024 13:20
@soyuka soyuka changed the base branch from main to 3.3 June 27, 2024 07:37
@soyuka soyuka force-pushed the fix/openapi-export-yaml-should-numeric-key-as-string branch from 4324754 to 5a47d5a Compare June 27, 2024 07:38
@soyuka soyuka force-pushed the fix/openapi-export-yaml-should-numeric-key-as-string branch from 5a47d5a to ede5bf5 Compare June 27, 2024 07:38
@soyuka soyuka merged commit af34e72 into api-platform:3.3 Jun 27, 2024
1 check passed
@soyuka
Copy link
Member

soyuka commented Jun 27, 2024

thanks!

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