You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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!
The text was updated successfully, but these errors were encountered:
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
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
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!
The text was updated successfully, but these errors were encountered: