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
As @johannesduesing mentioned: "The only issue i can see is that you are currently able to re-assign a component to the same instance that it is already using, which is actually triggering a re-assignment call to the registry. I would expect to either hide the currently used dependency or just give the user a message that re-assignment is not needed because the desired dependency is already established.
Since i remember talking with @janniclas about this i'm not sure if that's intended behaviour for this PR, so i will still approve it in the current state."
The question is how we want to handle this.
We could hide the connected components, but I thought it might be interesting for the admin to see the currently active connections during reconnect mode.
We can display an extra notification when trying to reconnect two already connected components (maybe the reassignment is wanted in some cases).
The text was updated successfully, but these errors were encountered:
As @johannesduesing mentioned: "The only issue i can see is that you are currently able to re-assign a component to the same instance that it is already using, which is actually triggering a re-assignment call to the registry. I would expect to either hide the currently used dependency or just give the user a message that re-assignment is not needed because the desired dependency is already established.
Since i remember talking with @janniclas about this i'm not sure if that's intended behaviour for this PR, so i will still approve it in the current state."
The question is how we want to handle this.
The text was updated successfully, but these errors were encountered: