Centralize file path validation for issue providers #1268
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR centralizes the file path validation logic that was previously duplicated across multiple issue providers (MsBuild, TAP, and SARIF) into a single, reusable method on the
BaseIssueProvider
class.Problem
The
ValidateFilePath
method existed in three different implementations with similar but slightly different logic:BaseMsBuildLogFileFormat.ValidateFilePath
- validated absolute paths onlyBaseTapLogFileFormat.ValidateFilePath
- handled both relative and absolute paths with auto-detectionSarifIssuesProvider.ValidateFilePath
- took an explicitisAbsolutePath
parameterThis duplication made the codebase harder to maintain and could lead to inconsistent behavior across providers.
Solution
Added a centralized
BaseIssueProvider.ValidateFilePath
static method that:(bool Valid, string FilePath)
All existing provider implementations now delegate to this centralized method:
Benefits
Testing
Fixes #975.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.