🐛 [BUG]: The connect bug on the basic example page

[zzc-1024]

Is there an existing issue for this?

• I have searched the existing issues and this is a new bug.

Current Behavior

• When I connect two nodes of the same handle type which is incorrect, it automatically changes the handle of the node connection.
• The order of Handle connections will affect whether the connection can be successful.

Expected Behavior

• When the user is connected incorrectly, the connection should be rejected.
• Whether the connection is successful or not should be independent of the connection order.

Steps To Reproduce

website

_2024_10_25_20_15_46_977.mp4

_2024_10_25_20_17_33_906.mp4

Relevant log output

No response

Anything else?

No response

[bcakmakoglu]

Thanks for the report. I’ll take a look once I’m back from vacation 👍

[bcakmakoglu]

What happens here is that with ConnectionMode.Loose (which is currently the default, although with 2.0 ConnectionMode.Strict will be the default mode) allows source <--> source and target <--> target connections but this requires handles to have a fixed id, otherwise VueFlow has to assume that the handle types that should be used are source <--> target (since the ids are null by default).

It's not great atm but a fix for this would be a breaking change, thus this will be fixed in 2.0 and not in any of the next patch/minor releases, sorry.

I'll keep this issue open to track it for the next major release though.

[zzc-1024]

Thank you for your patient answer.😃