Zijn er workarounds om alternatieve tagstructuren te ondersteunen?
Bijvoorbeeld, we willen tags introduceren voor elk van onze SDK’s die een weerspiegeling zijn van de SDK-naam. Onze SDK’s zijn gestructureerd als @namespace/name - idealiter is dit wat elke tag zou zijn, maar het lijkt niet mogelijk.
Ideeën?
Aside from the issue of presentation, hierarchy does exist, you can have Tag Groups.
For sure - we’ll be putting all the SDK tags under an SDK tag group. It’s just the actual tag themselves that’s the problem.
It’s made worse by the fact the name could be hyphenated as such @namespace/name-name. The perfect solution would be for that to be the tag in it’s entirety, as changing it to namespace_namename or any variation would defeat the purpose
hyphens are legal in tag names, not so sure about slashes
they are illegal because they are used in the routing.
Ahhhh yes - just need to figure out / and @
I appreciate the insights!
slashes are illegal because they would break the routing.
you talking about coding?
Not sure I fully follow, but we have 70+ SDKs we want to support via tags. They all follow the structure outlined, and looking for a viable solution to showing these SDKs as tags (either out of the box, custom etc)
My current thinking is to drop the namespace, and have just the name. Then use the Tag Icons to better indicate that these are the SDK versions, rather than generic tags
Would a | or a \ work, though?
No, those don’t work.
Did you ever find a solution? If so, please share it here.
Otherwise we’ll let this topic close as unfortunately the syntax you are asking for does not work for tags, as discussed above. Perhaps you could decorate your tags using the @ icon to at least get the @ prefix to show, using Tag Icons.
I thought I had updated 
- we did find a solution that works for us 
We removed the @namespace/ and simply used the name, alongside an SDK tag icon to denote it being one of our SDKs
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
