-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Naming conflict with source generator #479
Comments
Thanks for the report. I'll fix it. |
Environment |
I'm also having this issue related to MessagePipe and InGameDebugger. I followed the steps here https://vcontainer.hadashikick.jp/optimization/source-generator.
VContainer 1.13.0 @hadashiA How do I utilise #480 in my Unity project? Please advise. |
I have a solution to avoid similar problems until the pull request #480 is released. You can place the source generator in a separate assembly definition, for example, VContainer.Generators. This way, MessagePipe or any definition assembly will not trigger the source generator unless you add VContainer.Generators to the reference. Alternatively, you can install the latest version of VContainer from the Git URL according to the instructions on the Install via UPM (using Git URL) page and do not specify the version number. Then you can get a sneak peek at features that have not yet been released. |
@chikacc @spikeliu1984 @th3d0g Sorry for the late response. I've released a fix. https://github.com/hadashiA/VContainer/releases/tag/1.13.1 |
Description
Expected Behaviour
All clean, everything is happy.
Current Behaviour
Generated
Class1GeneratedInjector.g.cs
:Unity console shown as follows:
Environment
The text was updated successfully, but these errors were encountered: