UI and front end for new Conan metadata fields
-
Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA
What does this MR do and why?
UI and front end for the Conan metadata fields. This is linked to issue #33892 (closed).
The backend for this code is in !161048 (closed), not merged yet. But the database fields has been already added and merged in !157481 (merged).
The original design for the new metadata was the following (see below). But this is not relevant anymore as it was from 5 years ago and the UI changed. I put the new proposal in the screenshots section.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
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
- Have a a conan package in your local env
- Go to http://127.0.0.1:3000/[project path]/conan/-/packages/[package id]
- If the backend is not ready yet. It is possible you don't see the values then, as the extraction of the data did not happen, then you maybe need to add the data in DB manually if you want to test
Questions
It is my first MR for the front end. So, I have some question?
- First, do I need a feature flag, or should we just wait for the backend MR to be merged and after merge this one?
- I suppose we always need to do a UX review first. Next time, is there a way to have a UX review first on only a mock up before the whole code is done?
- For the Compiler Information, I used the code Icon. Is is ok, but is would be nice to have a "compiler" icon, is there a way to ask UX for new icon? I don't really have the knowledges to create new icons.
CC @ScanianJP