[
https://issues.apache.org/jira/browse/TINKERPOP-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Mallette updated TINKERPOP-2348:
----------------------------------------
Affects Version/s: 3.4.11
> Enable nullable checks
> ----------------------
>
> Key: TINKERPOP-2348
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2348
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Affects Versions: 3.4.11
> Reporter: Florian Hockmann
> Assignee: Florian Hockmann
> Priority: Minor
>
> Gremlin.NET should enable [nullable
> checks|https://devblogs.microsoft.com/dotnet/embracing-nullable-reference-types/]
> to clearly communicate to users what can be {{null}} in Gremlin.NET and also
> to possibly find possible {{NullReferenceExceptions}} easier in our own code.
> The recommendation from Microsoft is to update libraries during the so-called
> _"nullable rollout phase"_ which ends in November with the expected release
> of .NET 5 which should have nullable checks enabled by default.
> We can add .NET Core 3.1 as an additional target framework to get the
> nullable checks and still also target .NET Standard to stay platform
> independent and to also still support .NET Framework and older .NET Core
> versions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
