0
Fixed

Override Reference isn't checked on Ludiq.PeekCore.Runtime.asmdef

Victor Assmundsson 10 months ago updated by Lazlo Bonin (Lead Developer) 9 months ago 3

Hi,

When importing Peek I had some class name collisions due to the PeekCore.Runtime assembly referencing a dll from another plugin. Once the source was identified it was easily mitigated by checking the Override References box on the assembly definition, but I don't want to have to that every time I update and would prefer having that box already checked when importing the plugin files.

Regards,
Victor

Unity Version:
2020.1.6f1
Peek Version:
1.1.9
GOOD, I'M SATISFIED
Satisfaction mark by Victor Assmundsson 9 months ago
Working on Fix

Hi Victor,

Thanks for the heads up, I'll make sure to fix this in a future version.

I'm guessing the other assemblies were using types in the global namespace? I don't see how a collision could occur otherwise.

Hi Lazlo,

Thanks for the quick reply.
Yes, the other assembly defined types in the global namespace.

Regards,
Victor

Fixed

Hi Victor,

This has been fixed in v.1.3.1. Thanks again for the report.