swagger-api / swagger-api/swagger-ui
New to React and NodeJS: Rendering openapi 3.1 spec results in stack trace
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
If I render OAS 3.0 specs, I get no issue. But when I try to render an OAS 3.1 spec, I get this stack trace when using the latest 5.29.3 version. I am new to React and NodeJS so not sure if it is my bug or not:
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
Start by reproducing the reported rendering failure with an OpenAPI 3.1 specification in Swagger UI 5.29.3 and inspect the stack trace shown in the attached image. The issue is complete when the same specification renders without the reported stack trace; the issue does not name a source file or test to begin with.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, openapi, react
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100