Disable compiler warnings for non-nullable strings#228
Open
Mbucari wants to merge 1 commit intogisinternals:mainfrom
Open
Disable compiler warnings for non-nullable strings#228Mbucari wants to merge 1 commit intogisinternals:mainfrom
Mbucari wants to merge 1 commit intogisinternals:mainfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When adding the nuget package to a project with nullable reference types enabled, the three null string assignments cause analyzer warnings. Since you're targeting netstandard2.0 which only supports C# 7.3, you can't add a
#nullable disablestatement to GdalConfiguration.cs. So the only option remaining is to just disable that waning in the source file.Nullable reference types is only available in C#, not VB.NET