Sample update #6
Annotations
12 warnings
build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-dotnet@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build:
lib/Middleware/HttpMessageFormatter.cs#L70
Non-nullable field '_streamTask' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build:
lib/Middleware/HttpMessageFormatter.cs#L70
Non-nullable property 'HttpResponseMessage' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
build:
lib/Middleware/HttpMessageFormatter.cs#L84
Non-nullable field '_streamTask' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
build:
lib/Middleware/HttpMessageFormatter.cs#L84
Non-nullable property 'HttpRequestMessage' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
build:
lib/Middleware/HttpMessageFormatter.cs#L110
Possible null reference return.
|
build:
sample/Utilities/StringBuilderHttpMessageLogger.cs#L17
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
build:
sample/Utilities/DotNetILoggerHttpMessageLogger.cs#L20
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
build:
sample/Utilities/ConsoleHttpMessageLogger.cs#L7
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
build:
sample/Program.cs#L14
Possible null reference argument for parameter 'contentRoot' in 'IHostBuilder HostingHostBuilderExtensions.UseContentRoot(IHostBuilder hostBuilder, string contentRoot)'.
|
build:
test/ResourceManager.cs#L11
Possible null reference return.
|