Micha Reiser

Thanks for reporting this. This is obviously very annoying. We added the new settings in the latest ty version but we obviously want to avoid showing this warning for older...

I think asking users to use `ty: ignore[unused-ignore-comment]` seems reasonable. An alternative to this is to introduce a separate rule for unused `type: ignore` comments, which a user could disable.

I assume this is about the widening of `foo`. There has been some discussion about a strict-mode setting in https://github.com/astral-sh/ty/issues/527, which this relates to . I'm sure Carl or Alex...

Interesting, I'm unable to reproduce this but maybe it's because I'm using VS Code or because my example is too simple? If I have: ```py class Test: def __init__(self): ......

It's somewhat intentional that clicking on the constructor returns a reference to both. I need to double-check why this wasn't working for me in VS Code. The idea is that...

Thanks for the report. yes, this looks like a bug

The proper solution here depends on what exactly the issue author is looking for. Adding a CLI flag to hide warning diagnostics is certainly something we can do. However, this...

> But only errors will block our CI, and I want other devs in the team to clearly see them when they happen Thanks. That's helpful. As another alternative design....

Pyrefly seems to be the only type checker that accepts this but I'm not sure why (I'm not a typing expert myself). All other type checkers (Pyright, mypy) reject this...

Thanks for offering your help and creating an issue first. We already have a [JUnit reporter](https://github.com/astral-sh/ruff/blob/997dc2e7ccfc378d60e1b98c3fd244eb6b37ba70/crates/ruff_db/src/diagnostic/render/junit.rs#L22) for Ruff and ty shares that infrastructure with Ruff. That means, adding the JUnit...