Broken markdown link referencing "media type range"
See original GitHub issueOn the OpenAPI specs page for Request Body Object what is loaded in my browser looks like this (note the highlighted text):
I believe that comes from /versions/3.1.0.md but the Markdown looks correct to me:
The key is a media type or [media type range](https://tools.ietf.org/html/rfc7231#appendix-D) and the value describes it.
I tried copy+pasting the surrounding section over to the markdown-it online demo to see if maybe the table syntax was buggy, but it renders correctly there.
Is there a possibility that the published version (at spec.openapis.org/oas/latest.html
) is not actually generated from the latest markdown file?
I’m not sure what else to do to be helpful, sorry!
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
RFC 7763: The text/markdown Media Type
RFC 7763 The text/markdown Media Type March 2016 Table of Contents 1. ... With reference to the "paradigmatic use case" (i.e., collaborative Markdown...
Read more >GitLab Flavored Markdown (GLFM)
GitLab Flavored Markdown renders GitLab-specific references. For example, you can reference an issue, a commit, a team member, or even an entire project ......
Read more >Markdown Syntax | YouTrack Server Documentation - JetBrains
The YouTrack Markup Reference page provides a sandbox. Use the sandbox to preview ... Create sections in your content with thematic breaks.
Read more >R Markdown Lesser-Known Tips & Tricks #4: Looks Better ...
The R Markdown file format combines R programming and the markdown ... tab) allows you to create tabsets in a wider range of...
Read more >Basic Syntax - Markdown Guide
To create a line break or new line ( <br> ), end a line with two or more spaces, and then type return....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We always welcome PRs, and in this case against
main
. Not sure how to test it though, but will be happy to give it a shot.Thanks for bringing this up. My guess is that this is a rendering issue related to anchored URL. We’ll need to take a look at the generation process in order to solve it.