Introduce feature flag that enables preserving unchanged Markdown in the Content Editor
What does this MR do and why?
This MR introduces a feature flag that hides a new Markdown deserializer for the Content Editor. This new deserializer is client-side instead of using the Markdown Rest API.
When the feature flag is on, the client-side Markdown deserializer is activated.
Screenshots or screen recordings
This MR doesn’t introduce user-facing changes.
How to set up and validate locally
- Edit a Wiki page using the Content Editor
- Turning off and on the feature flag should switch the Content Editor between the rest API and the client-side deserializer
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #355787 (closed)
Edited by Enrique Alcántara