We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
Using media-type-examples-override, having in your example a field call operationId break the example replacement.
I'm sorry, I don't know how to add correct yaml into github issue.
Expected behavior Example with operationId variable is managed
Redocly Version(s) Docker image 1.25.15
To Reproduce
media-type-examples-override: -> operationIds: -> -> myEndpoint: -> -> -> request: -> -> -> -> application/mymediatype-1+json: /spec/examples/mymediatype/mymediatype-request.yaml
#Acceptable mymediatype-request.yaml content WorkingExample: -> summary: MyExampleSummary -> value: {"operationzId": "myoperation"}
#Refused mymediatype-request.yaml content BreakingExample: -> summary: MyExampleSummary -> value: {"operationId": "myoperation"}
#Bundle configuration content example.txt
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Using media-type-examples-override, having in your example a field call operationId break the example replacement.
I'm sorry, I don't know how to add correct yaml into github issue.
Expected behavior
Example with operationId variable is managed
Redocly Version(s)
Docker image 1.25.15
To Reproduce
media-type-examples-override:
-> operationIds:
-> -> myEndpoint:
-> -> -> request:
-> -> -> -> application/mymediatype-1+json: /spec/examples/mymediatype/mymediatype-request.yaml
#Acceptable mymediatype-request.yaml content
WorkingExample:
-> summary: MyExampleSummary
-> value: {"operationzId": "myoperation"}
#Refused mymediatype-request.yaml content
BreakingExample:
-> summary: MyExampleSummary
-> value: {"operationId": "myoperation"}
#Bundle configuration content
example.txt
The text was updated successfully, but these errors were encountered: