Skip to content

Add pyrefly non-exhaustive match as error - #1549

Merged
adamtheturtle merged 1 commit into
mainfrom
chore/pyrefly-non-exhaustive-match-20260215
Feb 15, 2026
Merged

adamtheturtle merged 1 commit into
mainfrom
chore/pyrefly-non-exhaustive-match-20260215

Conversation

@adamtheturtle

@adamtheturtle adamtheturtle commented Feb 15, 2026 •

Copy link
Copy Markdown
Member

Adds \ to \ in project \ files.


Note

Low Risk
Low risk config-only change that makes pyrefly stricter by failing on non-exhaustive-match, which may introduce new CI/lint failures but doesn’t affect runtime behavior.

Overview
Configures pyrefly to treat errors.non-exhaustive-match as an error by adding a new [tool.pyrefly] section to pyproject.toml, making non-exhaustive match cases fail type-checking.

Written by Cursor Bugbot for commit 4688961. This will update automatically on new commits. Configure here.

@adamtheturtle
adamtheturtle merged commit 09965e9 into main Feb 15, 2026
12 of 15 checks passed
@adamtheturtle
adamtheturtle deleted the chore/pyrefly-non-exhaustive-match-20260215 branch February 15, 2026 12:20

This branch was previously deployed

1 inactive deployment
development — 4688961e Deployed Feb 15, 2026 by adamtheturtle via pages #391
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant