Fine-grained property scoping

[glad burrow]

Properties are created with a global scope. While this works great for reusability, it could limit the new Tag functionality.

Consider generic property names such as status or type:

• When tagging a node with NetworkDevice, I expect type to allow values like "wireless" or "wired".
• When tagging it with GymWorkout, I expect values such as "strength" or "cardio".

With the current behavior, we cannot freely use generic properties as they will end up containing values from mixed contextes.

We can currently work around this limitation by using a different property name (i.e., NetworkType or WorkoutType). However, it would be great to have tag-scoped attributes.

[queen iris]

Something similar was brought up some months ago https://discord.com/channels/725182569297215569/1395733327545372813

[near vault]

https://www.loom.com/share/593da64e5af64fc8bb748605610f14ee

[glad burrow]

I wasn’t aware of that setting. Thank you for pointing it out, @near vault!

As long as choice properties have a limited, manageable set of values, I can see this working well. Honest question though: what happens (or should) when a new value is introduced? Will it automatically be available on every property usage?

I’ve just tested this on the mobile client (iOS, 2.0.0, 51634b4) and, unfortunately, the menu is partially hidden. It works flawlessly in the browser, though.

[near vault]

The mobile app should be updated now.