A tag and tags container components.
I'm ready to develop something similar to the Bulma CSS tag style and options if this idea is accepted 馃檪.
Thanks!

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.
What would be the difference from TaxonomyPicker control?
https://pnp.github.io/sp-dev-fx-controls-react/controls/TaxonomyPicker/
or the goal is to display the tags with different colors and and will be integrated with the Microsoft Teams "Tags" options or other dataset? such us TermSet?
The TaxonomyPicker is an input component while this one is a reusable component for displaying data consistently.
Pretty much like the tag element from Bulma (reference)
It will provide some options for the colour (danger, info, success, custom, etc), shape (normal, rounded), size (small, normal, large), etc.
Below are some usage examples of the tag component



Got it, i was imagine that but wanted to understand if is only output base on some type of dataset.
All good ideas are appreciated and dont know if there is a team that validates what get's in or out, just need to add value and i can see there value.
You can always create a new branch based on dev and send the PR to the sp-dev-fx-controls-react. I did the same like you, asked before, but in the end you just need to create PR and provide the description and value associated.
I definitely like the idea
Sounds like an interesting addition to me. I used similar components in the past but Fluent UI doesn't seem to have us covered in this case so I went with something custom and simple at the time. If they were available here, I would 100% have used them.
Hi all,
Some ideas which can be gathered from material ui
Hope this helps
Great! I got some more ideas from that. Thanks!
Got it, i was imagine that but wanted to understand if is only output base on some type of dataset.
All good ideas are appreciated and dont know if there is a team that validates what get's in or out, just need to add value and i can see there value.
You can always create a new branch based on dev and send the PR to the sp-dev-fx-controls-react. I did the same like you, asked before, but in the end you just need to create PR and provide the description and value associated.
I see. I'm just following the guideline to ask first before developing a new component. 馃榾
Thanks!
I definitely like the idea
Sounds like an interesting addition to me. I used similar components in the past but Fluent UI doesn't seem to have us covered in this case so I went with something custom and simple at the time. If they were available here, I would 100% have used them.
Thanks!
I guess I will start developing this component then create the PR and see whether it's acceptable or not 馃槃
Most helpful comment
Great! I got some more ideas from that. Thanks!
I see. I'm just following the guideline to ask first before developing a new component. 馃榾
Thanks!
Thanks!
I guess I will start developing this component then create the PR and see whether it's acceptable or not 馃槃