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.

Sign up for GitHub

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

Jump to bottom

The type in OpenAPI of the "OneToMany" property is always output as "array of string" #5713

Closed
ttskch opened this issue Aug 3, 2023 · 4 comments
Closed

The type in OpenAPI of the "OneToMany" property is always output as "array of string" #5713

ttskch opened this issue Aug 3, 2023 · 4 comments

Comments

@ttskch
Copy link
Contributor

ttskch commented Aug 3, 2023

API Platform version(s) affected

  • 3.1.x-dev
  • 3.2.x-dev

Description

The type in OpenAPI of the "OneToMany" property is always output as "array of string" regardless of the serialization config.
This problem is not reproduced in 3.1.12, but reproduced in 3.1.x-dev and 3.2.x-dev.
@stale
Copy link

stale bot commented Oct 2, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 2, 2023
@ttskch
Copy link
Contributor Author

ttskch commented Oct 2, 2023

Does anyone see this as a problem...? 😓

@stale stale bot removed the stale label Oct 2, 2023
@soyuka
Copy link
Member

soyuka commented Oct 17, 2023 •
edited
Loading

I don't understand if there's a type this should work, please provide a reproducer and a failing test

@ttskch
Copy link
Contributor Author

ttskch commented Nov 8, 2023

I checked again with v3.2.2 and the problem is no longer reproduced. Closing this issue.

@ttskch ttskch closed this as completed Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@soyuka @ttskch