question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Openapi.yaml file is not consistent to api.json

See original GitHub issue

Describe the bug We are using desing first for our REST-Api The openapi.yaml file in swagger-ui, which is rendered with smallrye/openapi i think is not consistent with the api.json used to generate our REST- endpoints. Vendor-Extensions of Path-Parameters are rendered on the operation not the Parameter.

Expected behavior Vendor-Extensions of Path-Parameters are rendered on the parameter.

Actual behavior Vendor-Extensions of Path-Parameters are rendered on the operation.

To Reproduce It is easy to reproduce this directly in the smallrye codebase (https://github.com/smallrye/smallrye-open-api/issues/376)

Configuration

# Add your application.properties here, if applicable.

Screenshots (If applicable, add screenshots to help explain your problem.)

Environment (please complete the following information):

  • Output of uname -a or ver: MINGW64_NT-10.0-18363 XXX 3.0.7-338.x86_64 2019-11-21 23:07 UTC x86_64 Msys
  • Output of java -version: openjdk 11.0.5 2019-10-15 LTS
  • GraalVM version (if different from Java):
  • Quarkus version or git rev: 1.5.2Final
  • Build tool (ie. output of mvnw --version or gradlew --version):

Additional context I think this is not directly a quarkus bug but it makes quarkus harder to use for us and our project. Perhaps this report can be used as tracking bug for upstream

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:11 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
phillip-krugercommented, Jul 6, 2020

Definitely before the next Quarkus release, so that we can get that in. We can also do this earlier if needed.

1reaction
gsmetcommented, Jun 26, 2020
Read more comments on GitHub >

github_iconTop Results From Across the Web

Importing v3.0 openAPI yaml/json is not working while ...
1.import the yaml file from above git repo and try to import while creating the API it will create fine. 2.While importing V3.0...
Read more >
OpenAPI Specification - Version 3.0.3 - Swagger
Note: While APIs may be defined by OpenAPI documents in either YAML or JSON format, the API request and response bodies and other...
Read more >
Open API with separate files not working properly : IDEA-284305
I am affected by the same issue. Multiple files, the main one with URIs and other resources imported with $ref on a paths...
Read more >
Working in YAML (OpenAPI tutorial) | Documenting APIs
YAML is a superset of JSON​​ For example, the Swagger UI can read the openapi. json or openapi. yaml files equivalently. Pretty much...
Read more >
OpenAPI 3.0 spec that conforms to JSON:API
After searching and searching online for an example of an OpenAPI 3.0 spec that conforms to JSON:API and coming up short, I decided...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found