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

Dealing with nested structs (again) and OpenAPI v3 - deepObject #87

Open
excavador opened this issue Jan 7, 2024 · 0 comments
Open

Comments

@excavador
Copy link

excavador commented Jan 7, 2024

Hello!

I am familiar with #59 and #61 and your decision to reject "nested structs", but at the same time I want to drag your attention to OpenAPI v3.x

There is the link to document about query parameters serialization

Please, pay attention to part about "deepObject".
To make possible to use your library with OpenAPI based server/client, you need to support one-level of nested object for query and form parameters

nickname[equal]="foo"&age[in]=1&age[in]=2&...

Also please pay attention there: https://github.com/go-playground/form

I totally understand your decision to reject "complex query parameters", but at the same time - how to deal with these kind of servers and these kind of query parameters?

You can like or dislike them, but in the real world you have the cases, where you need to deal with them.
Without some solution, I could not use your library :( I like it a lot, but at the same time I must to find some solution how to deal with nested objects in query parameters (show-stopper to me)

Thank you!

@excavador excavador changed the title Dealing with nesting structs (again) and OpenAPI v3 - deepObject Dealing with nested structs (again) and OpenAPI v3 - deepObject Jan 7, 2024
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

No branches or pull requests

1 participant