Skip to content

feat: reserve tool entry key for build backends - #121

Merged
henryiii merged 4 commits into
mainfrom
reserve-config-settings
Nov 19, 2026
Merged

henryiii merged 4 commits into
mainfrom
reserve-config-settings

Conversation

@henryiii

@henryiii henryiii commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Reworked this to be "tool", to keep it open for future additions. I like this much better than the specific config-settings.

🤖 AI text below 🤖

Reserves tool in each [[tool.dynamic-metadata]] entry for build backends. Like the top-level [tool] table, it holds one table per backend, and each backend defines its own contents. For scikit-build/scikit-build-core#1632 this gives tool.scikit-build.config-settings, which maps plugin settings to backend config-settings.

  • The loader removes tool together with provider, so a plugin never receives it. The loader does not check its contents.
  • The JSON schema requires tool to be a table.
  • The spec text is in docs/backend_authors.md, with a note that loaders from before 0.7 pass the key through to the plugin.

A [[tool.dynamic-metadata]] entry may set config-settings, a table that maps
plugin setting names to backend config-setting names. The loader validates it
and removes it with provider, so a plugin never receives it.

Assisted-by: ClaudeCode:claude-opus-5-5
@henryiii
henryiii force-pushed the reserve-config-settings branch from 6b31cce to 36e5d1d Compare November 18, 2026 20:43
Assisted-by: ClaudeCode:claude-opus-5-5
Backends get per-entry tables under tool.<backend>, like the top-level tool
table, so scikit-build-core uses tool.scikit-build.config-settings.

Assisted-by: ClaudeCode:claude-opus-5-5
@henryiii henryiii changed the title feat: reserve config-settings entry key for the backend feat: reserve tool entry key for build backends Nov 19, 2026
Assisted-by: ClaudeCode:claude-opus-5-5
@henryiii
henryiii merged commit 6b48b9a into main Nov 19, 2026
11 checks passed
@henryiii
henryiii deleted the reserve-config-settings branch November 19, 2026 15:28
@henryiii henryiii mentioned this pull request Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant