-
Notifications
You must be signed in to change notification settings - Fork 6k
Can't generate v3 spec by 3.0.0 cli #6517
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
Comments
Same issue, very annoying. Either don't push the 3.0 spec on people by only providing the documentation for that version, or make sure your other tools work as well :-( |
Well, they released the 3.0 spec to indicate that they are not going to change it and the devs of the tools can expect that the spec is solid and stable now. |
That's fair, but releasing a spec is not the same as actively hiding the older version of the spec. If tooling is not ready for 3.0, I'd like to be able to easily get to the 2.0 docs. I do realise though, that that is not an issue for the swagger-codegen github. |
damn, I've just spent a day massaging my swagger spec to fit v3 schema and now it's pointless :/ I wish the default docs were in sync with the currently released version. It's quite confusing to advertise openapi v3 on the homepage, and also link to swagger codegen which only supports v2. |
The 3.0 Snapshots seem to not even work with it yet :'(
|
Built my jar from the 3.0.0 branch today. It's still failing to read the "openapi" spec. Fails for json input and yaml input (stacktraces like here in the thread before). But the editor works with 3.0.0. I am sad. Is there any hint for a date when we plan to release a codegen-cli for OAS 3? |
I watch this thread for details about either release news, or when the snapshot will begin to show signs of supporting openapi 3.0, but no news yet ---> #4669 |
Please see #7003 for an experimental implementation of the generator engine in Node.js which supports OpenAPI 3.0 |
Just pulled https://hub.docker.com/r/swaggerapi/swagger-codegen-cli/tags/ latest version and still getting the same error, any updates on this since Nov? |
Same here. What is the point of releasing specification that is dead on arrival? |
hey @travis-sobeck , @StanislawSwierc , @poppinlp |
It somewhat works in a sense that is parses the specification! More than parsing I care about code generation and it doesn't seem to be at the right level. As you can tell from the second stack trace I've run it on Windows. typescript-angular
Java
|
We know about this issue, i hope it could be fixed next week. |
@HugoMario Since I'm a windows admin with a windows machine ... I rely on docker. Looks like the the container hasn't been updated in awhile https://hub.docker.com/r/swaggerapi/swagger-codegen-cli/ so I forked master today and tried to build a container based off the Dockerfile in master. It threw the following error |
@HugoMario I added that COPY line into the Dockerfile, ran build and that didn't really go well. |
hey @StanislawSwierc, sorry for late response. the path error has been already fixed, can you please check and let me know if it's still present. |
@travis-sobeck , can you please file that error in a new issue? |
I'm going to close this issue since we can generate now v3 spec using 3.0.0 cli. |
Same issue with swagger-codegen-cli-3.0.0-rc1.jar |
Same problem with |
Same problem
Error:
|
swaggerapi/swagger-codegen-cli-v3 works fine. |
I just git cloned the repo and changed to branch 3.0.0. I got the exact same error:
|
Make sure you rebuild the jar by running |
Description
I got an email which says 3.0.0 spec is officially released. So i came to here and downloaded this 3.0.0 cli jar and use it to generate code. It works for v2 spec YAML. But generate v3 spec YAML with this error log:
Seems it can't parse v3 spec T_T
Swagger-codegen version
This jar from your snapshot list.
Swagger declaration file content or url
The v3 spec is from your guide page:
Command line used for generation
Steps to reproduce
Download that jar and generate that demo spec.
Should i add some special arguments to active v3 support? Thanks.
The text was updated successfully, but these errors were encountered: