-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Clarification regarding reflecting rest parameters in OpenAPI specification #3448
Comments
https://spec.openapis.org/oas/v3.1.0#style-values Explode true for matrix ends up with
|
This issue has been labeled with |
20 similar comments
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
This issue has been labeled with |
Hi everyone, sorry about the noise on this pull request, we have some new automation and apparently it is still settling in! I think I've removed the label that was causing this behaviour, please accept our apologise and proceed as normal. @baywet Could you take a look at this please? I just added the author feedback label today and it immediately started adding the recent-activity thing, repeatedly 😱 |
This issue has been labeled with |
1 similar comment
This issue has been labeled with |
@lornajane sorry about the confusion this caused here. Here is a PR to address the many issues #3457 |
Thank you @commonism for the prompt response and the provided example. I've reviewed the example with explode-style encoding and explode set to true. However, it still doesn't quite match with the behavior I'm observing with Ballerina rest parameters in the resource path. After having some discussions, we decided to map this scenario in another way using wildcard path in OAS. You can refer the issue I have created regarding this here: ballerina-platform/ballerina-library/issues/5816 |
This also falls under #2653 and is likewise being addressed through the Moonwalk project (see links in that issue's last comment). |
Hi Team!
I am working with Ballerina OpenAPI tool, specifically utilizing rest parameters in the path of a resource function, where they act as an array. For example:
This allows us to send a request like:
GET albums/title1/title2/title3
In the resulting URL, these parameters are concatenated with
%2F
(encoded value for/
), and it looks like:http://{hostName}:{port}/albums/title1%2Ftitle2%2Ftitle3
I am seeking guidance on how to accurately reflect this behavior in the OpenAPI specification. Specifically, I would like to understand how to handle parameter serialization using the
style
andexplode
attributes in this scenario.Could you provide insights or examples on how to properly represent this scenario in the OpenAPI specification. Is there a proper way to do that?
#1459
The text was updated successfully, but these errors were encountered: