mirror of https://github.com/astral-sh/ruff
9cdac2d6fb
This adds a new `backend: internal | uv` option to the LSP `FormatOptions` allowing users to perform document and range formatting operations though uv. The idea here is to prototype a solution for users to transition to a `uv format` command without encountering version mismatches (and consequently, formatting differences) between the LSP's version of `ruff` and uv's version of `ruff`. The primarily alternative to this would be to use uv to discover the `ruff` version used to start the LSP in the first place. However, this would increase the scope of a minimal `uv format` command beyond "run a formatter", and raise larger questions about how uv should be used to coordinate toolchain discovery. I think those are good things to explore, but I'm hesitant to let them block a `uv format` implementation. Another downside of using uv to discover `ruff`, is that it needs to be implemented _outside_ the LSP; e.g., we'd need to change the instructions on how to run the LSP and implement it in each editor integration, like the VS Code plugin. --------- Co-authored-by: Dhruv Manilawala <dhruvmanila@gmail.com> |
||
|---|---|---|
| .. | ||
| build-binaries.yml | ||
| build-docker.yml | ||
| ci.yaml | ||
| daily_fuzz.yaml | ||
| mypy_primer.yaml | ||
| mypy_primer_comment.yaml | ||
| notify-dependents.yml | ||
| pr-comment.yaml | ||
| publish-docs.yml | ||
| publish-playground.yml | ||
| publish-pypi.yml | ||
| publish-ty-playground.yml | ||
| publish-wasm.yml | ||
| release.yml | ||
| sync_typeshed.yaml | ||
| ty-ecosystem-analyzer.yaml | ||
| ty-ecosystem-analyzer_comment.yaml | ||
| ty-ecosystem-report.yaml | ||
| typing_conformance.yaml | ||
| typing_conformance_comment.yaml | ||