fix(platform): Fix unexpected connection clash on two dynamic pins link with the same keys #8252
+25
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
When you connect a dynamic input pin with the same key, both pins will always be treated identically.
The example above: output is connected to #key1, but the #key1 on the other non-connected block also loses its input field indicating it's also connected
Changes 🏗️
Fix connection checking by adding nodeId into the equation.
Testing 🔍
Note
Only for the new autogpt platform, currently in autogpt_platform/