Feature Request: return parsed markdown body (html body) via API

[meteorlxy]

Description

Currently, we can only get the raw body (markdown string) of issues/comments via API. i.e. the body field:

Hope we can generate parsed body (HTML string) via API.

• Github API: use custom media type application/vnd.github.v3.html+json to return body_html field - REF
• Gitlab API: have another markdown API to parse markdown string to HTML string by users - REF
• Bitbucket API: return content.html by default - REF

[westurner]

How does /api/v1/markdown work?

[meteorlxy]

It's similar to Gitlab's implementation.

It works, but when fetching list of comments, we have to call /api/v1/markdown several times.

[westurner]

(I haven't looked at the code yet.) Is the rendered markdown HTML stored in the database or rendered for every request?

[meteorlxy]

I haven't looked at the code yet

Me neither 😅 In fact, I'm not familiar with this project

[westurner]

I took a quick look for my first time:

https://github.com/go-gitea/gitea/blob/master/models/issue.go

• RenderedContent

https://github.com/go-gitea/gitea/blob/master/routers/api/v1/api.go

https://github.com/go-gitea/gitea/blob/master/routers/api/v1/repo/issue.go

https://github.com/go-gitea/gitea/blob/master/routers/api/v1/misc/markdown.go

[westurner]

(t activates the GitHub file finder)

[lunny]

So I think this could be closed?

[westurner]

Where is and when was this feature implemented?