Tested a bit more, seems to work well. Should be merged into 4.6 since it fixes a bug for a feature that was just merged. #106341

just rebased, will work on this soon

I have managed to fix the initial "bug" with saving the class name of the variable in the DraggedExport struct and checking it against the property type hint.

While this does work, like you said it seems to be a separate problem. If you also change the type of the @export variable, it does not reset the value and keeps it assigned. Fixing this would have to be done in a separate PR since it doesn't have to do with drag-n-drop export variables, its just how export variables work in general.

There is an issue and PR about it: #104323, #104338
The change was introduced here: #84446

Anyways, updated to fix the original bug that this exposes with the name collision. Changing the type while the name collision error is happening does work correctly so I think it's fine. Don't like how it adds yet another for loop where if its a giant class it will run through a lot of properties, but I don't see a work around. It does only run once when the script doesn't have errors anymore though, so I think its fine.

Thanks!