Yes that’s correct Andy, thanks for explaining your thoughts with the design.
Personally, I like any solutions that save on graph space, even minimal space.
I utilize the “User Text” node as a “get” style component to query all values or keys of a model object but typically am only interested in seeing the values and not the keys or vice versa.
It is fine to have all connections showing at all times but it is nice to be able to hide what isn’t being used.
As an example:
In this image when collapsed we can see explicitly which inputs/outputs are influencing the node operation but if these were “always visible” the user doesn’t know if the default values have been overridden or not and have to check each one when troubleshooting/studying a node operation.
Separately a wishlist item would be to be able to set the user text node to “Search” where an input Key or Value would act as a filter and return corresponding Key/Value pair.
I made a user object cluster to do this but would love to have this be a default feature of the user text node.
User Object Node (Graph Space):
User Object Node (Internals):
