Introduced granular control to Monaco tag
What does this MR do?
!61112 (merged) introduced the globally preloaded Monaco chunk. However, it had some performance consequences despite the odss. This MR takes the process several steps further by doing the following:
- Introduces the mechanism of controlling whether to include Monaco on a view or not using
:monaco_tag
- Introduce the new helper for
prefetch
resource hint to complement the preloading of the resources - Updates all existing instances of the Source Editor-enabled routes to eagerly preload or prefetch the chunk
Screenshots (strongly suggested)
No visual changes except for now preloading/prefetching Monaco explicitly on some routes.
Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
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
/labels frontend ~performance performance-refinement devopscreate ~"group::editor" Source Editor