Frontend: Display GitLab-maintained and official badges for components
Summary
This issue is to track the work related to displaying GitLab-maintained and official (3rd party) badges for components that will get displayed in the catalog
Proposal
For whoever picks this up: Referencing a field like : resourceCertification which will have strings like gitlab-certified, etc. so on the Frontend, we can use that to display the proper badge.
Confirm purpose and User Reception (how does this benefit the user?)
Displaying badges shows to users which ones stand out more that are GitLab-maintained as well as official badging from 3rd parties.
Additional details
Some relevant technical details, if applicable, such as:
- Does this need a feature flag?
- Does there need to be an associated instrumentation issue created related to this work?
- Is there an example response showing the data structure that should be returned (new endpoints only)?
- What permissions should be used?
- Is this EE or CE?
-
EE -
CE
-
- Additional comments:
Implementation Table
| Issue title | Link | Relation/Notes |
|---|---|---|
Backend: Add verification_level database field to catalog_resource_components table |
#434053 (closed) | Blocks all |
verification_level is populated |
||
verified |
||
| Backend: Expose field in GraphQL | #434059 (closed) | in parallel |
Backend: create table ci_catalog_verified_namespaces
|
#439390 (closed) | Blocks #432272 (closed) #433299 (closed) |
| Frontend: Sort component by "verified author" components | #432272 (closed) | Blocked by #439390 (closed) |
partner, community, unverified |
||
Verified Creator badge for display |
||
Backend: Implement search algorithm for recommended
|
TBD |
Links/References
Edited by Mark Nuzzo