Summary
This is not a request for a way to forward on arbitrary configuration flags to ty from uv check -- I"m not sure we need a solution to be that general. But the specific use case in astral-sh/ty-pre-commit#7 seems quite reasonable to me, and the only thing the user is asking for there is a way to specify a custom ty configuration file. This would enable them to have two invocations of the ty-pre-commit hook in their pre-commit config file: one invocation would point to one ty config file, and the other invocation would point to the other ty config file. One would be fast to complete (suitable for running regularly as part of local development); the other would be slow to complete (you'd only run it manually or in CI rather than on every commit).
Example
No response
Summary
This is not a request for a way to forward on arbitrary configuration flags to ty from
uv check-- I"m not sure we need a solution to be that general. But the specific use case in astral-sh/ty-pre-commit#7 seems quite reasonable to me, and the only thing the user is asking for there is a way to specify a custom ty configuration file. This would enable them to have two invocations of the ty-pre-commit hook in their pre-commit config file: one invocation would point to one ty config file, and the other invocation would point to the other ty config file. One would be fast to complete (suitable for running regularly as part of local development); the other would be slow to complete (you'd only run it manually or in CI rather than on every commit).Example
No response