Comment by calmbonsai 2 days ago
I see zero need for this given that excellent time-testing code formatting tooling options are already available.
This smacks of feature-creep and I won't be incorporating it into any pipelines for the foreseeable future.
You realize this is just a shortcut for one of those "time-tested" options, right? ruff format is already widely used.
go fmt, cargo fmt, deno fmt, dart format, etc. it's hardly a new trend to ship a formatter with an all-in-one package manager for a language. It's convenient for new projects to not have to set up an additional dependency.
I'm not clear on this, but does it not also setup a backward dependency between the new project and uv?
Oh no I would hate to have to depend on my package manager and build system
`uv format` is just a front-end for `ruff format`. It isn't introducing a new formatter to the ecosystem or anything like that.