Frontend: Create the ability to control a `Verified Creator` badge for display
Summary
With storing Verified Creator namespaces noted in #439390 (closed), this issue is intended to extend on the discussion in #439477 (comment 1747252742) to build an easy method so that namespaces can be identified as Verified Creator.
Proposal
TBD - consider adding an admin setting so that a limited access role can control setting the namespace as a Verified Creator.
Confirm purpose and User Reception (how does this benefit the user?)
Users that meet the criteria of being Verified will be able to see their own namespace as verified and any interested users can see the namespace as Verified as well.
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