Removed design management startupjs
What does this MR do and why?
Was doing some investigation on the performance of the issue page, and found that we are making a graphql call for design management on every issue, including ones that do not have design management, and it occurs prior to the rest of the JS loading. Few options for followups, including:
- Moving sidebar graphql queries to startup.js
- Only startup.js design management on issues that have design management
For now, I think it's best to just remove design management in startup.js, so that call will be async, at the same time as the sidebar queries.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
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.