Fixes issue #905 on the maintenance branch #920
Annotations
11 warnings
|
Analyze (csharp):
tests/MiniExcelTests/MiniExcelIssueAsyncTests.cs#L295
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Analyze (csharp):
tests/MiniExcelTests/MiniExcelIssueAsyncTests.cs#L223
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Analyze (csharp):
tests/MiniExcelTests/MiniExcelIssueAsyncTests.cs#L366
Dereference of a possibly null reference.
|
|
Analyze (csharp):
tests/MiniExcelTests/MiniExcelIssueAsyncTests.cs#L362
Dereference of a possibly null reference.
|
|
Analyze (csharp):
tests/MiniExcelTests/MiniExcelCsvTests.cs#L309
Non-nullable property 'c2' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Analyze (csharp):
tests/MiniExcelTests/MiniExcelCsvTests.cs#L308
Non-nullable property 'c1' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Analyze (csharp):
tests/MiniExcelTests/MiniExcelCsvTests.cs#L317
Non-nullable property 'c2' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Analyze (csharp):
tests/MiniExcelTests/MiniExcelCsvTests.cs#L315
Non-nullable property 'c1' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Analyze (csharp):
tests/MiniExcelTests/MiniExcelAutoAdjustWidthTests.cs#L155
Dereference of a possibly null reference.
|
|
Analyze (csharp):
tests/MiniExcelTests/MiniExcelAutoAdjustWidthTests.cs#L149
Dereference of a possibly null reference.
|
|
Analyze (csharp)
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
|