swagger-api / swagger-api/swagger-codegen-generators
Unable to run "spring" server code generation in Swagger 3.0
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 299
- Forks
- 439
- PR merge metrics
- No merged PRs in 30d
Description
Dear all,
I am experiencing the following issue when generating spring server code with the openapi 3.0 specification.
In particular, it seems there's an error server side that returns Http Status Code 500.
The errors are listed below.
generator3.swagger.io/v2/generate:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error)
index.js:1 Uncaught (in promise) Error: Internal Server Error
at index.js:1
at tryCatch (runtime.js:62)
at Generator.invoke [as _invoke] (runtime.js:296)
at Generator.e.(/anonymous function) [as next] (https://editor.swagger.io/dist/swagger-editor-standalone-preset.js:1:106213)
at step (asyncToGenerator.js:17)
at asyncToGenerator.js:28
This errors seem to happen on chrome, firefox and safari (find attached the error shown in chrome).
Am I wrong in something?
Thanks in advance for everything.
Best,
m
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure in editor.swagger.io using an OpenAPI 3.0 document and the Spring server generator, then inspect the request to generator3.swagger.io/v2/generate and its 500 response. A useful outcome would identify whether the specification or generator causes the error and confirm successful Spring server code generation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- spring
- Domain
- backend, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100