feat: add markdown editing mode to the rich-text editor - #3466
Open
ngoc-minh-do wants to merge 1 commit into
Open
feat: add markdown editing mode to the rich-text editor#3466ngoc-minh-do wants to merge 1 commit into
ngoc-minh-do wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Visual / Markdown toggle to the rich-text editor so a task description (or comment, project description, etc.) can be edited as raw GFM Markdown instead of through the WYSIWYG toolbar.
TipTap.vue): a segmented Visual | Markdown toggle appears next to the Save button while editing. In Markdown mode the toolbar and WYSIWYG surface are replaced by a monospace textarea. Switching modes is instantaneous and draft autosave (localStoragestorageKey) works in both modes.pkg/routes/api/v2/richtext.go): newPOST /api/v2/richtext/convertendpoint ({from: "html"|"markdown"}) reusing the existingrichtext.HTMLToMarkdown/richtext.MarkdownToHTMLconverters. It is stateless — mentions survive as plain text, matching the editor's lossy-format contract. Content remains stored as canonical HTML.Testing
TestHumaRichText_Convertcovering HTML→Markdown, Markdown→HTML, task-list conversion, and an invalidfromvalue (422).go test -run 'TestHumaRichText' ./pkg/webtests/passes.pnpm lint:fix(0 errors),pnpm lint:styles:fix,pnpm typecheck(no new errors).Screenshots
AI disclosure: this change was generated with AI assistance and reviewed locally before opening.