Add `view only` state to Token component
Problem
There is a use case for Tokens where users that don't have rights in a project to edit a feature, can only view items (tokens) but not remove them.
Initially identified on https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/15174#note_204526900
Solution
Add a view only
state to token component.
Example(s)
- https://material.io/design/components/chips.html#input-chips
- https://material.io/develop/web/components/chips/
Usage
A remove comes with the functionality to remove the token from the set. View only tokens cannot be removed from the set.
Dos and dont's
(Use this table to add images and text describing what’s ok and not ok.)
|
|
---|---|
Remove all interaction (including the remove icon) from view only token |
Change the look and feel of token |
Related patterns
(List any related or similar solutions. If none, write: No related patterns)
Links / references
Pattern checklist
Make sure these are completed before closing the issue, with a link to the relevant commit, if applicable.
-
Read our contribution guidelines, especially the For GitLabbers section. -
Create a Sketch file in your progress folder just for this pattern and make sure that: -
You have not created a duplicate of an existing pattern, symbol, layer style, or text style. -
You have used the proper method for creating the pattern depending on the complexity. Atoms and molecules are symbols, organisms are groups. -
Typography uses text styles. When applicable, colors use shared styles.
-
-
Ask a UXer to review your Sketch file, linking them to your latest commit so they know where to find it. If they have the capacity, they should assign themselves to this issue. -
QA of your Sketch file by the reviewer. -
Add your changes to the pattern library. When copying things over, watch out for duplicated symbols, layer styles, and text styles. Some of our recommended plugins can help you find and remove duplicates. -
QA of pattern library by the reviewer. -
Create an issue in the Design System to add the pattern documentation. Mark it as related to this issue. -
Add an agenda item to the next UX weekly call to inform everyone (if it's a new pattern, not yet used in the application).
Edited by Rayana Verissimo