uv/crates/uv-configuration at zb/python-dev - mirrors/uv

mirrors/uv

mirror of https://github.com/astral-sh/uv.git synced 2025-07-17 18:25:02 +00:00

History

Max Mynter ebb45bdba1 Align supported Config-settings with example in docs (#12947 ) Closes #12929 ## Summary Untag the `config-settings` value to support JSON schema according to the [docs](https://docs.astral.sh/uv/reference/settings/#config-settings). ```toml [tool.uv] config-settings = { editable_mode = "compat" } ``` <!-- What's the purpose of the change? What does it do, and why? --> ## Test Plan Verified using the "Even Better TOML" extension with paths to old and new `uv.schema.json`. ## Notes I could not reproduce the issue with either the `taplo` (on which Even Better Toml is built, afaik) and `check-jsonschema` CLI tools; with both old and new versions of the `uv.schema.json` validated the `pyproject.toml`. Maybe for these there is some additional regularization going on and that's also how a breaking case ended up in the docs? I'm unsure on how to test for this. After about an hour, the Even better TOML VSCode extension was the only way to reproduce failing validation. Let me know if I can do something else. <!-- How was it tested? -->	2025-04-17 12:57:53 -04:00
..
src	Align supported Config-settings with example in docs (#12947 )	2025-04-17 12:57:53 -04:00
Cargo.toml	Cache `which git` in `uv init` (#12893 )	2025-04-15 09:40:08 +00:00

Align supported Config-settings with example in docs (#12947 )

Closes #12929
## Summary
Untag the `config-settings` value to support JSON schema according to
the
[docs](https://docs.astral.sh/uv/reference/settings/#config-settings).
```toml
[tool.uv]
config-settings = { editable_mode = "compat" }
```
<!-- What's the purpose of the change? What does it do, and why? -->

## Test Plan
Verified using the "Even Better TOML" extension with paths to old and
new `uv.schema.json`.


## Notes
I could not reproduce the issue with either the `taplo` (on which Even
Better Toml is built, afaik) and `check-jsonschema` CLI tools; with both
old and new versions of the `uv.schema.json` validated the
`pyproject.toml`.

Maybe for these there is some additional regularization going on and
that's also how a breaking case ended up in the docs?
I'm unsure on how to test for this.

After about an hour, the Even better TOML VSCode extension was the only
way to reproduce failing validation.

Let me know if I can do something else.

<!-- How was it tested? -->

2025-04-17 12:57:53 -04:00

src Align supported Config-settings with example in docs (#12947 ) 2025-04-17 12:57:53 -04:00

Cargo.toml Cache which git in uv init (#12893 ) 2025-04-15 09:40:08 +00:00