Merge branch 'hotfix/9.0.2' into develop #578
428 new problems found by Qodana for .NET
Qodana for .NET
139 new problems were found
| Inspection name | Severity | Problems |
|---|---|---|
Use preferred body style (convert into method or operator with preferred body style) |
🔶 Warning | 43 |
Type member is never used (non-private accessibility) |
🔶 Warning | 26 |
Use preferred argument style for literal values |
🔶 Warning | 15 |
Keyword 'new' is required |
🔶 Warning | 7 |
'value' parameter is not used |
🔶 Warning | 6 |
Redundant using directive |
🔶 Warning | 5 |
Auto-property accessor is never used (non-private accessibility) |
🔶 Warning | 5 |
Use preferred braces style (enforce braces in 'if' statement) |
🔶 Warning | 4 |
Possible 'null' assignment to non-nullable entity |
🔶 Warning | 3 |
Mismatch of optional parameter value in overridden method |
🔶 Warning | 3 |
Possible 'System.NullReferenceException' |
🔶 Warning | 3 |
Potentially misleading parameter name in lambda or local function |
🔶 Warning | 2 |
Nullability attribute usage with declaration of void or value type |
🔶 Warning | 2 |
Return value of 'GetEnumerator' method call is never disposed |
🔶 Warning | 2 |
Redundant 'partial' modifier on type declaration |
🔶 Warning | 2 |
Base type is required |
🔶 Warning | 2 |
Use explicit or implicit modifier definition for type members |
🔶 Warning | 1 |
Use of obsolete symbol |
🔶 Warning | 1 |
Class with virtual (overridable) members never inherited (non-private accessibility) |
🔶 Warning | 1 |
Co-variant array conversion |
🔶 Warning | 1 |
Possible comparison of value type with 'null' |
🔶 Warning | 1 |
Member initialized value ignored |
🔶 Warning | 1 |
Redundant cast |
🔶 Warning | 1 |
Redundant type arguments of method |
🔶 Warning | 1 |
Method return value is never used (non-private accessibility) |
🔶 Warning | 1 |
💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report
Contact Qodana team
Contact us at qodana-support@jetbrains.com
- Or via our issue tracker: https://jb.gg/qodana-issue
- Or share your feedback: https://jb.gg/qodana-discussions
Details
This result was published with Qodana GitHub Action
Annotations
Check warning on line 156 in source/Nuke.Common.Tests/SettingsTest.cs
github-actions / Qodana for .NET
Potentially misleading parameter name in lambda or local function
The '_' name is typically reserved for parameters without usages
Check warning on line 114 in source/Nuke.Tooling.Generator/Generators/DataClassExtensionGenerator.cs
github-actions / Qodana for .NET
Potentially misleading parameter name in lambda or local function
The '_' name is typically reserved for parameters without usages
Check warning on line 45 in source/Nuke.Utilities/IO/RelativePath.cs
github-actions / Qodana for .NET
Nullability attribute usage with declaration of void or value type
Applying nullness annotation to value type is meaningless
Check warning on line 111 in source/Nuke.Utilities/IO/AbsolutePath.cs
github-actions / Qodana for .NET
Nullability attribute usage with declaration of void or value type
Applying nullness annotation to value type is meaningless
Check warning on line 61 in source/Nuke.Build/Host.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 196 in source/Nuke.Build/Logging.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 47 in source/Nuke.Tooling.Tests/OptionsTest.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 14 in source/Nuke.Utilities/Text/String.Truncate.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 103 in source/Nuke.SourceGenerators/StronglyTypedSolutionGenerator.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 206 in source/Nuke.Build/Logging.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 75 in source/Nuke.Tooling/ToolTasks.Run.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 41 in source/Nuke.Tooling.Tests/OptionsTest.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 196 in source/Nuke.Build/Logging.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 135 in source/Nuke.Common.Tests/SettingsTest.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 127 in source/Nuke.Common/Tools/Unity/UnityTasks.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 106 in source/Nuke.SourceGenerators/StronglyTypedSolutionGenerator.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 104 in source/Nuke.GlobalTool/Rewriting/Cake/AbsolutePathRewriter.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 35 in source/Nuke.Tooling.Tests/OptionsTest.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 206 in source/Nuke.Build/Logging.cs
github-actions / Qodana for .NET
Use preferred argument style for literal values
Inconsistent argument style: missing name identifier
Check warning on line 49 in source/Nuke.Tooling.Tests/ToolOptionsArgumentsTest.cs
github-actions / Qodana for .NET
Use preferred body style (convert into method or operator with preferred body style)
Code body does not conform to code style settings: use statement body
Check warning on line 33 in source/Nuke.Tooling.Tests/ToolOptionsArgumentsTest.cs
github-actions / Qodana for .NET
Use preferred body style (convert into method or operator with preferred body style)
Code body does not conform to code style settings: use statement body
Check warning on line 117 in source/Nuke.Tooling.Tests/ToolOptionsArgumentsTest.cs
github-actions / Qodana for .NET
Use preferred body style (convert into method or operator with preferred body style)
Code body does not conform to code style settings: use statement body
Check warning on line 125 in source/Nuke.Tooling.Tests/ToolOptionsArgumentsTest.cs
github-actions / Qodana for .NET
Use preferred body style (convert into method or operator with preferred body style)
Code body does not conform to code style settings: use statement body
Check warning on line 112 in source/Nuke.Tooling.Tests/ToolTasksLoggerTest.cs
github-actions / Qodana for .NET
Use preferred body style (convert into method or operator with preferred body style)
Code body does not conform to code style settings: use statement body
Check warning on line 112 in source/Nuke.Tooling.Tests/ToolOptionsArgumentsTest.cs
github-actions / Qodana for .NET
Use preferred body style (convert into method or operator with preferred body style)
Code body does not conform to code style settings: use statement body