Are there any workarounds to support alternate tag structures?
For example, we want to introduce tags for each of our SDKs that is a reflection of the SDK name. Our SDKs are structured as @namespace/name - ideally this is what each of the tags would be, but doesn’t seem possible.
Ideas?
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.
