DetachHead

i feel like this could cause false positives and should only do it in certain cases. maybe using a plugin (#22) to support it for specific things or maybe it's...

what about a `ModuleString` type that enforces that the string resolves to a valid module

this is mostly done in #285, though i also want it to complain when you set diagnostic severity overrides in the extension when you also have basedpyright config in `pyproject.toml`...

should see if there's a way to do this at the language server level

i thought i already raised an issue for this but i can't find it lol. im thinking we do this by supporting diagnostic severity overrides in [`executionEnvironments`](https://detachhead.github.io/basedpyright/#/configuration?id=sample-pyprojecttoml-file), for example: ```toml...

idk why pyright doesn't support it when mypy does. it's not even exclusive to basedmypy lol

in the mean time a workaround that should work in your case is using ruff to report deprecated type annotations instead using [the pyupgrade rules](https://docs.astral.sh/ruff/rules/#pyupgrade-up), since ruff supports [per-file ignores](https://docs.astral.sh/ruff/settings/#lint_per-file-ignores)

> im thinking we do this by supporting diagnostic severity overrides in [`executionEnvironments`](https://detachhead.github.io/basedpyright/#/configuration?id=sample-pyprojecttoml-file), for example: > > ```toml > executionEnvironments = [ > { root = "src/foo", reportDeprecated = false...

are these folding ranges? if so, vscode seems to add these on its own without pylance/pyright installed:  just to make sure we're on the same page, are you using...

alright, i just removed "pylance feature parity" because as far as i can tell the functionality doesn't come from pylance but vscode itself