[FE] Prevent editing binary blobs in Snippets
This is the step 2 in Actions Plan for #217786 (closed).
The issue has two sides to it:
- Disable editing the binary files when editing snippets. This involves frontend and UX in order to figure out how this information is supposed to be presented to the end-user
- Prevent sending mutation actions for binary blobs back to
updateSnippet
orcreteSnippet
GraphQL mutations. This is an additional layer of protection and prevents the breakage of GraphQL mutations for blobs that are not supposed to be editable.
Video recording of the current issue
Recorded on staging using https://staging.gitlab.com/-/snippets/1693198
This step would allow for:
- always enabling "Edit" button on snippets (at the time of writing, the button is disabled in the case at least one blob is binary)
- safer Snippet editing experience when editing of binary blobs is brute-forced by appending
/edit
to the URL
Availability and Testing
Please include a SET in MR(s) reviews. If the development is done outside of a feature flag, running package-and-qa
job is recommended.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.