Add Content Editor as an option when creating or editing a Wiki Page [RUN ALL RSPEC] [RUN AS-IF-FOSS]
What does this MR do?
This MR fixes:
- A button titled "Use new editor" is visible when the feature when the feature flag
wiki_content_editor
is turned on and markdown format is selected. - Clicking on the button should show the content editor instead of the markdown editor.
- A warning should appear telling people that the content editor is in beta. A button "switch to old editor" should be a part of the warning that switches content back to the old editor.
- Switching formats should not be allowed when in the new editor. You can switch formats only when you go back to the old editor.
- When switching back to the old editor, the content in the old editor should be restored (discarding any changes in the new editor).
- When in the old editor, the format dropdown is enabled again and the user can switch between the formats again.
Screenshots (strongly suggested)
State | Screenshot |
---|---|
Default state | |
Click on "use new editor" ~ Loading state | |
Content editor in action |
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because this feature is behind a feature flag.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #325201 (closed)
Edited by Himanshu Kapoor