fix: Parse.ParseUser.LogOutAsync optimization (#403)
#17
mtrezzaAnnotations
11 warnings
|
release
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
release:
Parse/Infrastructure/Data/ParseDataEncoder.cs#L124
XML comment has badly formed XML -- 'End tag was not expected at this location.'
|
|
release:
Parse/Infrastructure/Utilities/JsonUtilities.cs#L376
XML comment has badly formed XML -- 'End tag 'summary' does not match the start tag 'pre'.'
|
|
release:
Parse/Infrastructure/Utilities/JsonUtilities.cs#L377
XML comment has badly formed XML -- 'Expected an end tag for element 'summary'.'
|
|
release:
Parse/Infrastructure/Utilities/TaskQueue.cs#L16
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
release:
Parse/Platform/Users/ParseCurrentUserController.cs#L28
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
release:
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.
|
|
release:
Parse/Platform/Cloud/ParseCloudCodeController.cs#L40
'Uri.EscapeUriString(string)' is obsolete: 'Uri.EscapeUriString can corrupt the Uri string in some cases. Consider using Uri.EscapeDataString for query string components.'
|
|
release:
Parse/Platform/Users/ParseCurrentUserController.cs#L95
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
release:
Parse/Platform/Users/ParseUser.cs#L31
The variable 'ex' is declared but never used
|
|
release:
Parse/Platform/Users/ParseUser.cs#L113
The variable 'ex' is declared but never used
|