feat: store relative paths in file reports#3
Merged
Conversation
Add support for storing relative file paths in violation reports instead of absolute paths. This improves readability and portability of reports. Changes: - Add makeRelative() method to SniffRunner to convert absolute paths to relative paths based on current working directory - Update XmlFileProcessor.processFile() signature to accept optional reportPath parameter - Pass relative path through the processing pipeline to be used in FileReport - Add test coverage for relative path storage in file reports
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add support for storing relative file paths in violation reports instead of absolute paths.