feat: Upgrade target framework from NET Standard 2.0 to .NET 6.0 #72
Annotations
11 warnings
|
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/
|
|
Build:
Parse/Infrastructure/Data/ParseDataEncoder.cs#L129
XML comment has badly formed XML -- 'End tag was not expected at this location.'
|
|
Build:
Parse/Infrastructure/Utilities/JsonUtilities.cs#L376
XML comment has badly formed XML -- 'End tag 'summary' does not match the start tag 'pre'.'
|
|
Build:
Parse/Infrastructure/Utilities/JsonUtilities.cs#L377
XML comment has badly formed XML -- 'Expected an end tag for element 'summary'.'
|
|
Build:
Parse/Platform/Users/ParseCurrentUserController.cs#L37
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
Parse/Platform/Users/ParseCurrentUserController.cs#L50
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
Parse/Platform/Users/ParseCurrentUserController.cs#L86
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
Parse/Platform/Users/ParseCurrentUserController.cs#L134
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
Parse/Platform/Users/ParseCurrentUserController.cs#L28
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
Parse/Infrastructure/Utilities/TaskQueue.cs#L16
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
Parse/Platform/Installations/ParseInstallation.cs#L171
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.
|
Loading