You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "thing" about this is that the tag-name value (ie, "alert", "key", "tunnel") only provide the last part of the item tag-path which means it is impossible to select all UUIDs that belong to a given full-tag without the risk of collecting tags from different plugins that happen to have the same name.
Is there actually any straight-forward way to resolve this? I imagine that the flow on effects of expanding the tag value to include the full tag-path would create a whole set of new issues elsewhere.
@ndejong I think we should just add the attributes to the items, so you could point to something like {{tunnel.__uuid__}} I'll take a look at this when I can.
I started a discussion in the forum with the same subject but I think I need to move this one here to discuss the code in more detail.
My goal is to implement a template helper function called
getUUIDs()to facilitate being able to write the following template style:-Following the code, I observe that the special
__uuid_tags__attribute that is populated via this code... and this code provides data in the helper that looks like this
The "thing" about this is that the tag-name value (ie, "alert", "key", "tunnel") only provide the last part of the item tag-path which means it is impossible to select all UUIDs that belong to a given full-tag without the risk of collecting tags from different plugins that happen to have the same name.
Is there actually any straight-forward way to resolve this? I imagine that the flow on effects of expanding the tag value to include the full tag-path would create a whole set of new issues elsewhere.
@AdSchellevis - I'm figuring this question is for you.
The text was updated successfully, but these errors were encountered: