-
Notifications
You must be signed in to change notification settings - Fork 227
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
Compiler Warning CS0649 #420
Comments
No response.. Should I just submit a PR with the additional pragma statement? |
Sorry I missing this Tim, I was away all last week. |
sjh37
added a commit
that referenced
this issue
May 23, 2018
Thanks for the prod Tim. |
Released in v2.37.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a follow up to the issue raised in #328.
After this change, I get 3 compiler warnings per generated Fake context about CS0649. For example:
FakeContext._changeTracker' is never assigned to, and will always have its default value null FakeContext._configuration' is never assigned to, and will always have its default value null FakeContext._database' is never assigned to, and will always have its default value null
The suggestion by @StevenBonePgh in #328 was to edit
InitializePartial()
to explicitly set the values tonull
. Another option is to add a#pragma
along with the list of other disabled warnings.Should we go ahead and implement one of these approaches, or can the problem be resolved in another way?
The text was updated successfully, but these errors were encountered: