Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Merge requests
  • !18926

Merged
Created May 12, 2018 by blackst0ne@blackst0neDeveloper8 of 16 tasks completed8/16 tasks

Resolve "Expand API: Render an arbitrary Markdown document"

  • Overview 22
  • Commits 14
  • Pipelines 15
  • Changes 8

What does this MR do?

Adds /api/v4/markdown API endpoint to render markdown text.

Parameter Type Required Description
text String Yes The markdown text to render
gfm Boolean No (optional) Render text using GitLab Flavored Markdown
project String No (optional) The full path of a project to use as the context when creating references using GitLab Flavored Markdown

Notes

  1. There is no option to chose a markdown engine. The common_mark is used because [we are migrating to CommonMark] (#43011 (closed)).
  2. The endpoint was added only to APIv4 because APIv3 is deprecated and about to be dropped.

Todo

  • add documentation
  • add specs
  • leave a comment in the issue when this MR is merged

Are there points in the code the reviewer needs to double check?

No.

Why was this MR needed?

Improve API

Screenshots (if relevant)

No.

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • Documentation created/updated
  • API support added
  • Tests added for this feature/bug
  • Review
    • Has been reviewed by UX
    • Has been reviewed by Frontend
    • Has been reviewed by Backend
    • Has been reviewed by Database
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Squashed related commits together
  • Internationalization required/considered
  • End-to-end tests pass (package-and-qa manual pipeline job)

What are the relevant issue numbers?

Closes #19861 (closed)

Edited May 12, 2018 by blackst0ne
Assignee
Assign to
Reviewer
Request review from
11.0
Milestone
11.0 (Past due)
Assign milestone
Time tracking
Source branch: 19861-expand-api-render-an-arbitrary-markdown-document