Skip to content

Refactor CSV and Excel enumerators for improved performance and clarity #76

Refactor CSV and Excel enumerators for improved performance and clarity

Refactor CSV and Excel enumerators for improved performance and clarity #76

Triggered via pull request July 21, 2026 01:59
Status Success
Total duration 3m 8s
Artifacts

codeql.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Analyze (C#): src/ExcelReader.Core/Parser/Internal/RowEnumeratorBase.cs#L78
Do not declare visible instance fields (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1051)
Analyze (C#): src/ExcelReader.Core/Parser/Internal/RowEnumeratorBase.cs#L77
Do not declare visible instance fields (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1051)
Analyze (C#): src/ExcelReader.Core/Parser/Internal/RowEnumeratorBase.cs#L16
Fix this implementation of 'IDisposable' to conform to the dispose pattern.
Analyze (C#): src/ExcelReader.Core/Parser/Internal/RowEnumeratorBase.cs#L21
Do not declare visible instance fields (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1051)
Analyze (C#): src/ExcelReader.Core/Parser/Internal/RowEnumeratorBase.cs#L22
Do not declare visible instance fields (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1051)
Analyze (C#): src/ExcelReader.Core/Parser/Internal/RowEnumeratorBase.cs#L16
Provide an overridable implementation of Dispose(bool) on 'SyncRowEnumerator' or mark the type as sealed. A call to Dispose(false) should only clean up native resources. A call to Dispose(true) should clean up both managed and native resources. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1063)
Analyze (C#): src/ExcelReader.Core/Writer/Internal/CellFormatter.cs#L90
All 'WriteNumber' method overloads should be adjacent.