Create download blob viewer
What does this MR do?
This MR add an "download" blob viewer. This is part of a bigger effort to refactor the repository browser. There is no new UI/UX changes introduced, the behaviour is the same as original HAML version.
| HAML Version | This MR |
|---|---|
 |
 |
| Live Example: https://gitlab.com/sming-gitlab/sample-public-project/-/blob/master/blob/zip.zip | - |
| HAML Code > https://gitlab.com/gitlab-org/gitlab/blob/master/app/views/projects/blob/viewers/_download.html.haml | - |
Note: Yes you might notice the button group is displaying a few more buttons from the HAML version, there's a follow-up issue to address that > #335776 (closed)
Testing Case
This feature is behind a feature flag, to turn on:
rails c
Feature.enable(: refactor_blob_viewer)Here's a sample zip file you can use to trigger the "download" blob viewer.
- Navigate to Repository > Files.
- Click on the zip file.
-
You will see the download viewer. -
When clicked, you will download the file.
Screenshots or Screencasts (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are 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. -
This change is backwards compatible across updates, or this does not apply.
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 #324320 (closed)
Edited by Samantha Ming