Add metadata component to Package details page
What does this MR do?
This MR adds a new metadata component in the package details UI
To smoothly change the UI (to accomplish this#227582) iteratively without disturbing the users this work is gated behind a feature flag and split in several MRs
| Change | Mr |
|---|---|
| Add feature flag and new History Component | !38045 (merged) |
| Add additional metadata component |
|
| Move the installation commands to the center column, remove the feature flag and clean up old code | TBD |
As an experimental process, I would like to appoint a single reviewer and a single maintainer for all of the MRs, so that everyone has all the context.
- Reviewer: @oregand
- Maintainer @ntepluhina
How to test
To test this we will need to do some groundwork, luckily we can leverage the rails console for all of it:
rails cp = Project.find(1)FactoryBot.create(:npm_package, :with_build, project: p)FactoryBot.create(:conan_package, project: p)FactoryBot.create(:nuget_package, :with_metadatum, project: p)FactoryBot.create(:maven_package, project: p)Feature.enable(:packages_details_one_column, p)
After this, the feature will be enabled on the project with id 1 ( or any other selected on the second command ) and a npm, conan, nuget and maveng package will be created.
Note that the packages created with FactoryBot have fake data inside that may not match with the 'real' one
Screenshots
| Maven | Conan | Nuget | Npm ( no metadata ) |
|---|---|---|---|
 |
 |
 |
 |
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
- [-] Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers - [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] 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
Part of #227582 (closed)