Repository navigation
fix(findings): explain when ESLint ignores the selected scope - #448
Merged
Merged
Conversation
byronwall
marked this pull request as ready for review
November 22, 2026 20:18
byronwall
enabled auto-merge (squash)
November 22, 2026 20:18
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
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.
UX-017: Explain an unassessed ESLint result
ESLint can legitimately ignore every file in the selected scope. Its failure output may start with a generic banner before explaining the ignore or configuration condition. Findings used that banner as the entire reason.
Verification
git diff --checkpass. The broader findings test file has 21 passes and one project-ID fixture failure reproduced unchanged on the baseline in this sandbox.