JSON schema for `pyproject.toml` `[tool.pixi]`

[pavelzw]

Problem description

After adding pixi.toml to schemastore it would be nice to get the same for pyproject.toml.
Are the JSON schemas (apart from tool.pixi) exactly the same? If we do something like #1084 (comment), it wouldn't be exactly the same but a superset. I think [tool.pixi.tool] is not really necessary.

[olivier-lacroix]

Yes currently, the schema for tool.pixi is exactly the same

[ruben-arts]

I will leave this schema store PR here: https://github.com/SchemaStore/schemastore/pull/3315/files

What I understand from the pixi schema auto updates from main and the pyproject schema is that it is actually hard coded in the repo. Do you think they allow auto updates in these sub schema's.

Ping @henryiii, i've seen some of your PR's. Do you think it makes sense to already pixi to the pyproject.toml schema or does this require something?

[henryiii]

Subschemas must be in the repo currently. I've been just copying over files as needed when things release. Otherwise, it's easy to do, hatch for example has both a subsection and a standalone file. Ruff, cibuildwheel, black, scikit-build-core are all examples of projects that have a schema that can be produced (and sometimes stored in the package) that is also copied over manually to SchemaStore after releases.

[henryiii]

Also, if it's added, then validate-pyproject-schema-store will pick it up automatically.

[ruben-arts]

Awesome @henryiii thanks for the insight! 🙏

[bollwyvl]

Here is a lovely tox PR which encapsulates some tests and automation around the conventions for ensuring schema freshness on the de facto schema store.

tox already provided a tox schema command which prints out the schema-at-rest, a la #4338.