Skip to content

feat: add ty/pyrefly config fixtures and ty checks - #871

Draft
henryiii wants to merge 1 commit into
mainfrom
feat/typecheck-checks
Draft

henryiii wants to merge 1 commit into
mainfrom
feat/typecheck-checks

Conversation

@henryiii

@henryiii henryiii commented Oct 23, 2026 •

Copy link
Copy Markdown
Collaborator

🤖 AI text below 🤖

Follow-up to #870.

  • New ty and pyrefly fixtures read ty.toml / pyrefly.toml (which take precedence, as in ty itself) or the [tool.*] section of pyproject.toml. MY100 and MY101 use them, so standalone config files now work for MY101 too.
  • MY101 passes for ty if [tool.ty.rules] is set. For Pyrefly it now requires preset to be strict or all; before, any preset passed.
  • MY107: ty must set terminal.error-on-warning. ty exits 0 on warnings by default, so rules like unused-ignore-comment do not fail CI.
  • MY108: ty must enable blanket-ignore-comment (off by default), the equivalent of MyPy's ignore-without-code.

Option names and defaults were checked against ty 0.0.91 and Pyrefly 1.4.0. No new Pyrefly checks: the strict preset already reports unused ignores, and permissive-ignores is off by default.


📚 Documentation preview 📚: https://scientific-python-cookie--871.org.readthedocs.build/

Add `ty` and `pyrefly` fixtures that read ty.toml/pyrefly.toml or the
pyproject.toml section. MY101 now handles ty rules and requires a strict
Pyrefly preset. New MY107 (ty error-on-warning) and MY108 (ty
blanket-ignore-comment).

Assisted-by: ClaudeCode:claude-opus-5-5
@henryiii
henryiii marked this pull request as draft October 23, 2026 19:35

This branch has not been deployed

No deployments
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