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
A node lists its dependencies. When you go into edit mode for the node's dependencies, any of the dependencies that are not currently in the client's graph disappear.
This is an issue because people will be erasing valid dependencies by accident / slash won't be able to add new dependencies without erasing old.
To solve the issue, we should build some way to request info from the server without necessarily getting the entire nodes. Or I suppose it would be okay to get the entire nodes. All dependencies can theoretically exist in the clients "graph" but not necessarily in their "visible graph".
This should probably be a high priority to at least patch this for now.
The text was updated successfully, but these errors were encountered:
A node lists its dependencies. When you go into edit mode for the node's dependencies, any of the dependencies that are not currently in the client's graph disappear.
This is an issue because people will be erasing valid dependencies by accident / slash won't be able to add new dependencies without erasing old.
To solve the issue, we should build some way to request info from the server without necessarily getting the entire nodes. Or I suppose it would be okay to get the entire nodes. All dependencies can theoretically exist in the clients "graph" but not necessarily in their "visible graph".
This should probably be a high priority to at least patch this for now.
The text was updated successfully, but these errors were encountered: