swagger-api / swagger-api/swagger-ui

Markdown not rendered

Open
#2,745 14 comments 17 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

cat: rendering P2 type: bug version: 3.x
Dominant language
JavaScript
Stars
29k
Forks
9.3k
Avg merge
2d 23h
Merged PRs (30d)
25

Description

In responses, the markdown is not rendered

Current result:
captura de pantalla 2017-03-20 a las 16 59 06

You can see that the MD is not rendered

Expected result
the MD is rendered. Image from the editor , but rendering was similar in previous version of Swagger UI
captura de pantalla 2017-03-20 a las 17 07 09

How to reproduce

Paste this code in YAML API spec


responses:
  Error403:
    description: |
      ** Forbidden **
          
      Possible values
              
      | Error Name | Error Message  | 
      |--------|---|---|
      | FORBIDDEN | Forbidden  |
    schema:
          $ref: '#/definitions/Error'


And use it as response

Notes

  • Same behavior seems to occurs in other parts of the API spec interpretation ( tested in API call description and reproduced )

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with the provided YAML response description, then compare rendering in response descriptions and API call descriptions. Trace the Swagger UI entry point that interprets these Markdown fields; done means the bold text, image, and table render as Markdown in both reported locations.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.