We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
NonNullType
Session # 2 demonstrates how HC leverages C#'s nullable reference types. In Session # 6 NonNullType is used...
.ResolveWith<TrackResolvers>(t => t.GetSessionsAsync(default!, default!, default)) .UsePaging<NonNullType<SessionType>>()
...but it looks like it doesn't affect the generated schema at all.
The graphql type nullability is controlled by nullable reference types:
Task<IEnumerable<Session>> GetSessionsAsync
Session
Task<IEnumerable<Session?>> GetSessionsAsync
Sessions
Is it ok to remove the use of NonNullType if nullable reference types is enabled?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Session # 2 demonstrates how HC leverages C#'s nullable reference types.
In Session # 6
NonNullType
is used......but it looks like it doesn't affect the generated schema at all.
The graphql type nullability is controlled by nullable reference types:
Task<IEnumerable<Session>> GetSessionsAsync
for non-nullableSession
Task<IEnumerable<Session?>> GetSessionsAsync
for nullableSessions
Is it ok to remove the use of
NonNullType
if nullable reference types is enabled?The text was updated successfully, but these errors were encountered: