Implement Markdown editor, enforce formatting rules, and integrate new API fields #1171
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.
Proposed Changes
MarkdownEditorcomponent.markdown-to-jsx.MarkdownEditorto enforce the those formatting rules:b, strong, em, i, ul, ol, and p.h1-h6and link tagsa.ExerciseDetailEdit.tsxand the Add wizard (Step3Description.tsx):exerciseTranslation.descriptionSource(Markdown source) or falls back to description (legacy HTML).descriptionSourcefield in the API payload, completing the migration path established in the backend.Related Issue(s)
Please check that the PR fulfills these requirements