fix: insertion marker previewer finding wrong connection for different conn counts #7833
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.
The basics
The details
Resolves
Fixes N/A
Proposed Changes + Reasons
If the insertion marker block had more connections that the original block (e.g. for chameleon blocks) The insertion marker previewer could find the wrong connection and try to connect that.
How chameleon blocks work: If they were connected in a stack, when they start dragging, they add an output connection. Before this change, previews for the previous connection (previously the first connection) would grab the output connection of the insertion marker block (current first connection). This would cause the insertion marker to be positioned incorrectly, because the output couldn't connect where the previous connection is supposed to.
This makes is so that we fail early if the blocks don't match. And that makes the chameleon blocks work.
Test Coverage
Tested by linking with chameleon blocks. No more weird insertion marker positioning bugs.
Documentation
N/A
Additional Information
N/A