Remove get_sqlite_multiple_db_records, which nothing calls - #99
Merged
Conversation
The helper appended the full staged path as a Source Path column value and returned the prose "file path in the report below" as source_path, so it produced both of the defects the lint job now blocks: an examiner filesystem path in a report column, and a string constant where the "located at" line needs real paths. No artifact in any of the five cores calls it, and ALEAPP has never carried it at all. Removing it is better than repairing it: a repaired version is still an idiom for the next artifact to copy, and the two checks only see code that exists. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
The helper appended the full staged path as a Source Path column value and returned the prose "file path in the report below" as source_path, so it produced both of the defects the lint job now blocks: an examiner filesystem path in a report column, and a string constant where the "located at" line needs real paths.
No artifact in any of the five cores calls it, and ALEAPP has never carried it at all. Removing it is better than repairing it: a repaired version is still an idiom for the next artifact to copy, and the two checks only see code that exists.