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

[FEATURE REQUEST] Support Parameter formats #294

Closed
raveclassic opened this issue Nov 15, 2019 · 2 comments
Closed

[FEATURE REQUEST] Support Parameter formats #294

raveclassic opened this issue Nov 15, 2019 · 2 comments

Comments

@raveclassic
Copy link

Is your feature request related to a problem? Please describe.
Currently ws channel bindings allow you to define some query/header parameters: https://github.com/asyncapi/bindings/tree/master/websockets#channel-binding-object
However this solution lacks flexibility and power in comparison to swagger-2 or openapi-3 parameters. Especially in case of non-primitive parameters - there's no way to define how such parameters should be serialized. Swagger-2 spec has a collectionFormat and openapi-3 - style/explode for that.

Can't it be tackled using specification extensions?
IMO this should be part of the core spec.

Describe the solution you'd like
The best would be to replicate openapi-3 approach to describe parameters using in/style/explode (etc.) properties.

Describe alternatives you've considered
Not sure there're some which would allow the same level of flexibility and consistency.

Additional context
I'm writing a codegen tool based on swagger-2/openapi-3/asyncapi-2 specs which automatically handles connections that's why I need a solution to fully handle parameters.

@fmvilas
Copy link
Member

fmvilas commented Nov 18, 2019

Issue moved to asyncapi/bindings #8 via ZenHub

@fmvilas
Copy link
Member

fmvilas commented Nov 18, 2019

This issue belongs to the WebSockets binding, so I've moved it there.

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

2 participants