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

Body runtime expression issues in example arazzo docs #259

Open
TristanSpeakEasy opened this issue Sep 29, 2024 · 0 comments · May be fixed by #260
Open

Body runtime expression issues in example arazzo docs #259

TristanSpeakEasy opened this issue Sep 29, 2024 · 0 comments · May be fixed by #260

Comments

@TristanSpeakEasy
Copy link

Hi,

I was just going over the example Arazzo documents you have and I found some issues in the documents.

For example in https://github.com/OAI/Arazzo-Specification/blob/977f586da14b65bd8e612b763267b8b728749e52/examples/1.0.0/FAPI-PAR.arazzo.yaml:

[119:24] body reference must be empty or start with #: $response.body.request_uri
[135:17] body reference must be empty or start with #: $response.body.code

From my reading of the Arazzo specification I believe body runtime expressions like this should be $response.body#/request_uri ie the runtime expression to the body and then a json pointer to the field within.

This is based on the ABNF syntax here: spec.openapis.org/arazzo/latest.html#runtime-expressions

which defined the expression as "$response." source, source as source = ( header-reference / query-reference / path-reference / body-reference ) and body-reference as body-reference = "body" ["#" json-pointer ]

@TristanSpeakEasy TristanSpeakEasy changed the title Body runtime expression issues in examples arazzo docs Body runtime expression issues in example arazzo docs Sep 29, 2024
@frankkilcommins frankkilcommins linked a pull request Oct 23, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant