Add pyrefly non-exhaustive match as error#1948
Merged
Merged
Conversation
adamtheturtle
temporarily deployed
to
development
GitHub Actions
Inactive
adamtheturtle
deleted the
chore/pyrefly-non-exhaustive-match-20260215
branch
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.
Adds \ to \ in project \ files.
Note
Low Risk
Config-only change that affects lint/type-check output but does not alter runtime behavior; risk is limited to potentially failing CI due to stricter checks.
Overview
Adds a
pyreflyconfiguration block inpyproject.tomlto treatnon-exhaustive-matchdiagnostics as errors, tightening static-analysis enforcement for pattern matching.Written by Cursor Bugbot for commit 1b367dd. This will update automatically on new commits. Configure here.