Merge pull request #25 from decimo3/AutoRelease #3
Annotations
11 warnings
Build application
The target framework 'net7.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 application:
Helpers/Authorization.cs#L9
'HMACSHA256Algorithm' is obsolete: 'HMAC SHA based algorithms are not secure to protect modern web applications. Consider switching to RSASSA or ECDSA.'
|
Build application:
Helpers/Authorization.cs#L20
'HMACSHA256Algorithm' is obsolete: 'HMAC SHA based algorithms are not secure to protect modern web applications. Consider switching to RSASSA or ECDSA.'
|
Build application:
Startup.cs#L56
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
Build application:
Startup.cs#L57
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
Build application:
Startup.cs#L12
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 application:
Handles/HandleMessage.cs#L12
Non-nullable field '_instance' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
Build application:
Services/Logging.cs#L53
Cannot convert null literal to non-nullable reference type.
|
Build application:
Services/Logging.cs#L54
Cannot convert null literal to non-nullable reference type.
|
Build application:
Services/Logging.cs#L6
Non-nullable field '_loggerFactory' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
Restore dependencies
The target framework 'net7.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.
|
Loading