Replace ACE with Monaco for Snippets editing/creation
What does this MR do?
Replaces ACE editor with Monaco using the Editor Lite.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
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
Closes #198604 (closed)
Merge request reports
Activity
changed milestone to %12.9
1 Error dbe50cdb: Commits that change 30 or more lines across at least 3 files must describe these changes in the commit body Commit message standards
One or more commit messages do not meet our Git commit message standards.
For more information on how to write a good commit message, take a look at How to Write a Git Commit Message.
Here is an example of a good commit message:
Reject ruby interpolation in externalized strings When using ruby interpolation in externalized strings, they can't be detected. Which means they will never be presented to be translated. To mix variables into translations we need to use `sprintf` instead. Instead of: _("Hello #{subject}") Use: _("Hello %{subject}") % { subject: 'world' }
This is an example of a bad commit message:
updated README.md
This commit message is bad because although it tells us that README.md is updated, it doesn't tell us why or how it was updated.
Reviewer roulette
Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category (e.g. frontend or backend), and by a maintainer in all other categories.
To spread load more evenly across eligible reviewers, Danger has randomly picked a candidate for each review slot. Feel free to override this selection if you think someone else would be better-suited, or the chosen person is unavailable.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines.
Once you've decided who will review this merge request, mention them as you normally would! Danger does not (yet?) automatically notify them for you.
Category Reviewer Maintainer frontend André Luís ( @andr3
)Kushal Pandya ( @kushalpandya
)QA Grant Young ( @grantyoung
)Sanad Liaquat ( @sliaquat
)test Quality for spec/features/*
Tomislav Nikić ( @tmslvnkc
)No maintainer available Generated by
DangerEdited by 🤖 GitLab Bot 🤖added 365 commits
-
e31b17f2...2abc63f1 - 364 commits from branch
master
- ba24af40 - Support Monaco editor in Snippet edit form
-
e31b17f2...2abc63f1 - 364 commits from branch
added 550 commits
-
ba24af40...dcc1cd1b - 549 commits from branch
master
- 023f2b34 - Support Monaco editor in Snippet edit form
-
ba24af40...dcc1cd1b - 549 commits from branch
- Resolved by Denys Mishunov
@andr3 can not argue with Danger here :) Could you please do the first round of FE review here?
@mlapierre could you please review the feature specs in this MR? Thank you :)
assigned to @mlapierre and @andr3
- Resolved by Justin Boyson
- Resolved by Justin Boyson
- Resolved by Justin Boyson
unassigned @jboyson
- Resolved by Justin Boyson
@mishunov Looks good! Just a couple of non-blocking questions. I'll leave you to assign to maintainer after you have decided what to do with them.
added workflowin review label and removed workflowscheduling label
- Resolved by Mark Lapierre
Since I have updated QA Page object, we should involve QA into the process as well. And since ~"group::editor" has a an assigned counterpart in testing, I think it only makes sense to do what I had to do in the first place: involve @a_mcdonald :)
@a_mcdonald could you please review this one from the testing (QA and otherwise) standpoint? @mlapierre has already unofficially approved from ~Quality side, however.
assigned to @a_mcdonald and unassigned @mlapierre
unassigned @a_mcdonald
- Resolved by Kushal Pandya
Thank you very much @mlapierre and @a_mcdonald! Then I take it as both test and QA are approved and the MR is in proper shape to be sent to a maintainer.
@kushalpandya could you please take a look at this one and merge if it looks fine? Thank you
Edited by Denys Mishunov
assigned to @kushalpandya
- Resolved by Kushal Pandya
unassigned @kushalpandya
@kushalpandya your comment has been addressed. Thank you! Now back to you for the final round of review.
assigned to @kushalpandya
added database databasereview pending labels
removed database databasereview pending labels
added 363 commits
-
47d05b6b...ceffcc4c - 362 commits from branch
master
- 6832090c - Support Monaco editor in Snippet edit form
-
47d05b6b...ceffcc4c - 362 commits from branch
enabled an automatic merge when the pipeline for 598c4791 succeeds
The
package-and-qa
job from pipeline https://gitlab.com/gitlab-org/gitlab/pipelines/121858615 triggered https://gitlab.com/gitlab-org/build/omnibus-gitlab-mirror/pipelines/121867913 downstream.The
Trigger:qa-test
job from pipeline https://gitlab.com/gitlab-org/build/omnibus-gitlab-mirror/pipelines/121867913 triggered https://gitlab.com/gitlab-org/gitlab-qa/pipelines/121891801 downstream.The
gitlab-qa
downstream pipeline passed. .
mentioned in commit b2822028
added workflowstaging label and removed workflowin review label
added workflowcanary label and removed workflowstaging label
added workflowproduction label and removed workflowcanary label
mentioned in merge request gitlab-com/www-gitlab-com!44253 (merged)