Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #20923 Markdown replaces text in artifact REST route too
    Actions
    Infos
    #20923
    Clarck Robinson (robinsoc)
    2021-04-19 09:06
    2021-04-16 15:29
    22514
    Details
    Markdown replaces text in artifact REST route too

    Since the story #18337 markdown replace text:

    Existing comments and text fields that are in "Text" format can stay "Text" or switch to "Markdown" or "HTML"

    ATM, it still possible to create or update an artifact which contains a text field with the text format by using artifacts/ REST routes.

    Trackers
    development
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Clarck Robinson (robinsoc)
    Verified
    Empty
    Attachments
    Artifact links
    Empty
    Empty
    References
    Referencing request #20923

    Git commit

    tuleap/tuleap/stable

    request #20577 Invalid format can be set in DB at artifact submission via REST 722f262795
    User avatar Clarck Robinson (robinsoc) , 2021-04-21 09:44
    Referenced by request #20923

    Artifact Tracker v5

    story #18337 markdown replace text
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2021-04-19 09:06

    Hi,

    I fear this is not something we can change, removing the possibility to submit text fields as Text via the REST API means introducing a breaking change into the API.

    In the web UI the main goal was to not add yet another format to keep things simple, we do not have this constraint via the API.