Upgrade .NET from 6.0 to 8.0 #7516
Annotations
10 errors
Run coverage tests:
Backend/Startup.cs#L151
Possible null reference assignment.
|
Run coverage tests:
Backend/Startup.cs#L152
Possible null reference assignment.
|
Run coverage tests:
Backend/Helper/Language.cs#L46
Prefer comparing 'Length' to 0 rather than using 'Any()', both for clarity and for performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1860)
|
Run coverage tests:
Backend/Controllers/UserRoleController.cs#L111
Prefer a 'TryGetValue' call over a Dictionary indexer access guarded by a 'ContainsKey' check to avoid double lookup (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1854)
|
Run coverage tests:
Backend/Services/LiftService.cs#L144
Prefer a 'TryGetValue' call over a Dictionary indexer access guarded by a 'ContainsKey' check to avoid double lookup (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1854)
|
Run coverage tests:
Backend/Services/LiftService.cs#L36
Prefer comparing 'Length' to 0 rather than using 'Any()', both for clarity and for performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1860)
|
Run coverage tests:
Backend/Services/LiftService.cs#L162
Prefer a 'TryGetValue' call over a Dictionary indexer access guarded by a 'ContainsKey' check to avoid double lookup (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1854)
|
Run coverage tests:
Backend/Services/LiftService.cs#L193
Prefer a 'TryGetValue' call over a Dictionary indexer access guarded by a 'ContainsKey' check to avoid double lookup (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1854)
|
Run coverage tests:
Backend/Services/LiftService.cs#L217
Prefer comparing 'Length' to 0 rather than using 'Any()', both for clarity and for performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1860)
|
Run coverage tests:
Backend/Services/PasswordResetService.cs#L48
Prefer using 'string.Equals(string, StringComparison)' to perform a case-insensitive comparison, but keep in mind that this might cause subtle changes in behavior, so make sure to conduct thorough testing after applying the suggestion, or if culturally sensitive comparison is not required, consider using 'StringComparison.OrdinalIgnoreCase' (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1862)
|
Loading