swagger-api / swagger-api/swagger-ui
Swagger Responses section showing could not render with emojis
Open
Nobody has claimed this yet.
cat: rendering
specification: 3.x
type: bug
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Q&A (please complete the following information)
- OS: windows
- Browser: Chrome
- Version: [e.g. 22]
- Method of installation: npm
- Swagger-UI version: "swagger-parser": "^10.0.3", "swagger-ui": "^3.51.2",
- Swagger/OpenAPI version: OpenAPI 3.0.1
Content & configuration
Swagger Responses section showing could not render with emojis. Seeing same issue with swagger editor.
PFA
Example Swagger/OpenAPI definition:
api_response.txt
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 loading the attached api_response.txt definition in Swagger UI and reproducing the Responses section failure with emoji content. Compare the result with Swagger Editor and trace the rendering path for the Responses section; done means the supplied response renders without the “could not render” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, openapi
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100