Micha Reiser

Thanks for this suggestion. We don't currently have the capacity or expertise on the team to maintain those rules ourselves. But more than happy to support any work within ty...

The reason why I think it's related to #2031 is that it would be the most straightforward fix

> It depends how explicit this actually is in practice :) environment variables are often quite challenging to tie to explicit user intent, i.e., opposed to command-line flags. Yeah, VS...

Good to know. This should be very easy to implement.

Yes, this is a known limitation that ty only picks up your configuration if it's directly in the folder you opened in your editor or any of its ancestor directories.

I'll re-open this. While https://github.com/astral-sh/ruff/pull/22053 will help in the described instance, there will still be inconsistencies if the configuration file uses any relative paths (because the LSP resolves the paths...

We also don't support `.ty.toml`. The configuration file must be named `ty.toml` and the `src` option is `src.root = ["apps", "proj"]`. Python path is under `environment`, etc. See https://docs.astral.sh/ty/reference/configuration/#environment

I thought we discussed this before but I can't find the issue anymore. An option like this does make sense to me.

Okay, it has come up in https://github.com/astral-sh/ty/issues/278 and this will also be relevant for https://github.com/astral-sh/ty/issues/606

My current thinking on this is: * Add a new `analysis.type-ignore` that controls whether ty respects `type: ignore` comments (true) or ignores them (false). * Add a new `unused-type-ignore-comment` comment...