Fix: Handle renamed files in package_todo.yml validation #59
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.
Problem Description
The
danger-packwerkgem'spackage_todo_yml_changes.checkvalidation was failing when files were renamed in a PR. When a developer:fulfillment_document_service.rb→application_document_service.rb)bin/pks updateto updatepackage_todo.ymlwith the new filenameRoot Cause
When comparing violations from the "before" state (which referenced old filenames) to the "after" state (which referenced new filenames), the violation comparison logic didn't account for renamed files. The
BasicReferenceOffense#==method compares all fields including thefilefield, so violations with different file paths wouldn't match even if they represented the same violation on a renamed file.Solution
The fix normalizes file paths in violations when comparing them:
git.renamed_files