You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would expect the description_html field in the issues and intake API endpoints to be plain HTML, so that it can easily be integrated into other apps (without interfering with their hypothetical Tailwind styling or else without containing lots of meaningless classes). Reversely, I would like to be able to create new issues without having to worry about adding these class names so that it is rendered correctly in the Plane dashboard. Would it be possible to provide this styling from outside the rich text editor?
(Thanks for building and maintaining Plane; it's very useful! 👍)
Steps to reproduce
Make a request to /api/workspaces/21insure/projects/123/issues/123/ and see the classes it returns:
"description_html": "<p class=\"editor-paragraph-block\">E.g. in the person details step of the sales funnel:</p><ol class=\"list-decimal pl-7 space-y-2 tight\" data-tight=\"true\"><li class=\"not-prose space-y-2\"><p class=\"editor-paragraph-block\">Enter invalid password (e.g. <code class=\"rounded bg-custom-background-80 px-[6px] py-[1.5px] font-mono font-medium text-orange-500 border-[0.5px] border-custom-border-200\" spellcheck=\"false\">test</code>)</p></li><li class=\"not-prose space-y-2\"><p class=\"editor-paragraph-block\">Click Next. An \"invalid password\" message shows up </p></li><li class=\"not-prose space-y-2\"><p class=\"editor-paragraph-block\">Enter a valid password (e.g. <code class=\"rounded bg-custom-background-80 px-[6px] py-[1.5px] font-mono font-medium text-orange-500 border-[0.5px] border-custom-border-200\" spellcheck=\"false\">KOPwwnefk#123</code>)</p></li><li class=\"not-prose space-y-2\"><p class=\"editor-paragraph-block\">Click Next again. It will again report that an invalid password was provided, which wasn't the case the second time.</p></li></ol>"
Environment
Production
Browser
None
Variant
Self-hosted
Version
v0.24.1
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current behavior
I would expect the
description_html
field in the issues and intake API endpoints to be plain HTML, so that it can easily be integrated into other apps (without interfering with their hypothetical Tailwind styling or else without containing lots of meaningless classes). Reversely, I would like to be able to create new issues without having to worry about adding these class names so that it is rendered correctly in the Plane dashboard. Would it be possible to provide this styling from outside the rich text editor?(Thanks for building and maintaining Plane; it's very useful! 👍)
Steps to reproduce
Make a request to /api/workspaces/21insure/projects/123/issues/123/ and see the classes it returns:
"description_html": "<p class=\"editor-paragraph-block\">E.g. in the person details step of the sales funnel:</p><ol class=\"list-decimal pl-7 space-y-2 tight\" data-tight=\"true\"><li class=\"not-prose space-y-2\"><p class=\"editor-paragraph-block\">Enter invalid password (e.g. <code class=\"rounded bg-custom-background-80 px-[6px] py-[1.5px] font-mono font-medium text-orange-500 border-[0.5px] border-custom-border-200\" spellcheck=\"false\">test</code>)</p></li><li class=\"not-prose space-y-2\"><p class=\"editor-paragraph-block\">Click Next. An \"invalid password\" message shows up </p></li><li class=\"not-prose space-y-2\"><p class=\"editor-paragraph-block\">Enter a valid password (e.g. <code class=\"rounded bg-custom-background-80 px-[6px] py-[1.5px] font-mono font-medium text-orange-500 border-[0.5px] border-custom-border-200\" spellcheck=\"false\">KOPwwnefk#123</code>)</p></li><li class=\"not-prose space-y-2\"><p class=\"editor-paragraph-block\">Click Next again. It will again report that an invalid password was provided, which wasn't the case the second time.</p></li></ol>"
Environment
Production
Browser
None
Variant
Self-hosted
Version
v0.24.1
The text was updated successfully, but these errors were encountered: