-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Null Ref exception when using Roslyn generator #534
Comments
Ok I see, question: Do you have components with an context attribute like |
@sschmid Thank you for the quick answer 👍 Regarding your question, and after further investigation (we tried and succeeded reproducing it on a clean project), it seems that if you use the Roslyn plugin data providers for the very first code generation that you make - it will give you this exception, and therefor will not even generate the contexts themselves.. It seems like it needs the contexts to already be created before that.. but no code generation was done before that step. it's the very first time you try to generate.. So I believe the question is then why it fails when using Roslyn for the first time code generation? Thanks! |
@eransh22 great, that will help me a lot to find the issue. I will work on a fix for that. Thanks for the hints to reproduce |
I just ran into this as well and the cause was indeed trying to decorate a component with a context that hadn't yet been created. If it were not for this issue though I wouldn't have realized that was what I had done (It was a typo). Anyway to make the error more helpful? |
@eransh22 I just tried to reproduce, but unfortunately I cannot confirm. Generating the first time works great for me. But: the next release contains a bugfix for the exception you posted, maybe your issue was related to that. I will release a new version soon, let's see if that solves your issue already. @jwvanderbeck |
Hi, there are some fixes in Entitas 0.47.0 |
Hi,
We have found a bug which happens every time we generate code using Roslyn plugin.
The "doctor -v"command finish with this exception:
This is our preferences file:
Cheers
The text was updated successfully, but these errors were encountered: