Bump version to 3.0.3 #9
Annotations
13 warnings
Build
The target framework 'net5.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
|
Build
.NET Core 3.1 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
|
Build
.NET 5.0 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
|
Build
The target framework 'net5.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
|
Build:
tests/GraphQL.Upload.AspNetCore.Tests/TestSchema.cs#L19
'ComplexGraphType<object?>.Field<TGraphType>()' is obsolete: 'Please call Field<TGraphType>(string name) instead.'
|
Build:
tests/GraphQL.Upload.AspNetCore.Tests/TestSchema.cs#L29
'ComplexGraphType<object?>.Field<TGraphType>(string, string?, QueryArguments?, Func<IResolveFieldContext<object?>, object?>?, string?)' is obsolete: 'Please use one of the Field() methods returning FieldBuilder and the methods defined on it or just use AddField() method directly. This method may be removed in a future release. For now you can continue to use this API but we do not encourage this.'
|
Build:
tests/GraphQL.Upload.AspNetCore.Tests/TestSchema.cs#L39
'ComplexGraphType<object?>.Field<TGraphType>(string, string?, QueryArguments?, Func<IResolveFieldContext<object?>, object?>?, string?)' is obsolete: 'Please use one of the Field() methods returning FieldBuilder and the methods defined on it or just use AddField() method directly. This method may be removed in a future release. For now you can continue to use this API but we do not encourage this.'
|
Build:
tests/GraphQL.Upload.AspNetCore.Tests/TestSchema.cs#L29
'ComplexGraphType<object?>.Field<TGraphType>(string, string?, QueryArguments?, Func<IResolveFieldContext<object?>, object?>?, string?)' is obsolete: 'Please use one of the Field() methods returning FieldBuilder and the methods defined on it or just use AddField() method directly. This method may be removed in a future release. For now you can continue to use this API but we do not encourage this.'
|
Build:
tests/GraphQL.Upload.AspNetCore.Tests/TestSchema.cs#L39
'ComplexGraphType<object?>.Field<TGraphType>(string, string?, QueryArguments?, Func<IResolveFieldContext<object?>, object?>?, string?)' is obsolete: 'Please use one of the Field() methods returning FieldBuilder and the methods defined on it or just use AddField() method directly. This method may be removed in a future release. For now you can continue to use this API but we do not encourage this.'
|
Build:
tests/GraphQL.Upload.AspNetCore.Tests/TestSchema.cs#L19
'ComplexGraphType<object?>.Field<TGraphType>()' is obsolete: 'Please call Field<TGraphType>(string name) instead.'
|
Build:
tests/GraphQL.Upload.AspNetCore.Tests/TestSchema.cs#L19
'ComplexGraphType<object?>.Field<TGraphType>()' is obsolete: 'Please call Field<TGraphType>(string name) instead.'
|
Build:
tests/GraphQL.Upload.AspNetCore.Tests/TestSchema.cs#L29
'ComplexGraphType<object?>.Field<TGraphType>(string, string?, QueryArguments?, Func<IResolveFieldContext<object?>, object?>?, string?)' is obsolete: 'Please use one of the Field() methods returning FieldBuilder and the methods defined on it or just use AddField() method directly. This method may be removed in a future release. For now you can continue to use this API but we do not encourage this.'
|
Build:
tests/GraphQL.Upload.AspNetCore.Tests/TestSchema.cs#L39
'ComplexGraphType<object?>.Field<TGraphType>(string, string?, QueryArguments?, Func<IResolveFieldContext<object?>, object?>?, string?)' is obsolete: 'Please use one of the Field() methods returning FieldBuilder and the methods defined on it or just use AddField() method directly. This method may be removed in a future release. For now you can continue to use this API but we do not encourage this.'
|