swagger-api / swagger-api/swagger-ui
Inquiring about a previous issue
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Hi, I'm just wondering whether issue #4155 was ever solved? The issue was 'completed', but never mentioned in a PR and I'm having the same issues... I'm trying to add a description to the OpenApiInfo containing buttons that should help people to understand which buttons to press to try out our API:
I'm trying something like
"<button class=\"btn authorize locked\">Authorize</button>", but the classes are filtered out.
Can anyone provide me with more information about the status of #4155?
Kind regards.
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
Review issue #4155 and the OpenApiInfo description rendering path first, then reproduce the button markup with its class attributes. Determine whether the filtering is intentional and identify the expected handling for these classes; the issue is complete only when the agreed behavior is documented and verified with a reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- documentation, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100