renamed NullableContextOptions to Nullable #1573
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
resolved conflicts - this should be good go |
|
@david-driscoll @mholo65 @rchande can we get this in? at the moment nullable reference types is broken in omnisharp in the latest .net core 3.0 previews |
bjorkstromm
approved these changes
Aug 9, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
since vs 16.2p1 the msbuild property to enable nullable reference types is called
Nullableinstead ofNullableContextOptions(this is LDM decision).see related PRs here: dotnet/roslyn#35516 and here dotnet/docs#12497
issue reported by @shoe-diamente - thanks!