Markdown Checkbox render issues

[q-wertz]

When adding tasks the text to the markdown checkbox is rendered in a new line in the "Title" field. In the "Description" field it is correct.

[lieut-data]

Thanks for the report, @q-wertz! Can you help me understand your use case that requires putting multiple lines in the title and embedded checkboxes within a task?

[q-wertz]

Hello,
using multiple lines in a title field does not seem to make sense, you are right. But as the functionality for multiline titles is available and works for everything despite checkboxes I use it to let users select some things (e.g. the services they need access to). This shouldn't be a task as then it counts to the done/undone tasks and it will never be 100%.

In this setup I use the Description field just for a small hint that they should fill it.

I could also change it to

just wanted to let you know the issue as (despite I kind of misuse the title field) it still looks like a bug. (and it seems strange that lists which are also multiline objects are working but not the checkboxes)

[lieut-data]

just wanted to let you know the issue as (despite I kind of misuse the title field) it still looks like a bug. (and it seems strange that lists which are also multiline objects are working but not the checkboxes)

Understood, and thank you for the report! Agree that modelling this in the description is probably best for your use case the way things work currently. I also agree that we should look into disabling some markdown functionality in this case, e.g. lists and checkboxes don't make sense in the header.

@hmhealey, do you know if we have the flexibility to choose what we "support" when rendering markdown?

[hmhealey]

Not at the moment. I have ideas for how to do that in my one-day-we'll-get-to-it ideas for Markdown, but the current version doesn't support that except for extra things we add like at-mentions and hashtags.