Remember pipeline drawer expanded state in local storage
What does this MR do?
The drawer default is now open in the pipeline editor section and if someone collapses it, it will be loaded collapsed the next time someone comes to the section. The reverse is also true.
Note that it's behind a disabled feature flag pipeline_editor_drawer
This MR CANNOT be merged until !60957 (merged) is merged
| Description | MR link |
|---|---|
|
|
!60856 (merged) |
|
|
!60957 (merged) |
| Remember collapse state in local storage | You are here |
| MR to enable by default | Coming soon in a theatre near you |
| Rollout issue | #329806 (closed) |
Screenshots (strongly suggested)
Note that the transition "bug" where we see the drawer move into place will be addressed in a follow-up
Screen_Recording_2021-05-07_at_12.20.36_PM
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
Related to #296547 (closed)
Edited by Frédéric Caplette