Add repo-level tap metadata config#27
Merged
eric-tramel merged 1 commit intocodex/epic-15-plugin-tapfrom May 7, 2026
Merged
Conversation
f5d5da3 to
7fad446
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the root
[tool.ddp.tap]metadata table for this repository and a sharedddp.tap_configloader with deterministic validation errors for missing or malformed config.Wires
ddp newscaffolding to that tap config so generated plugins use the configured package prefix, repository URL, docs base URL, author name, and default Data Designer dependency instead of hardcoded NVIDIA-specific values or the staledata-designer>=0.5.3requirement.Adds tests proving external-style tap values flow into generated scaffold output and proving missing/malformed config errors are clear.
Why
Issue #21 moves repository tap identity out of hardcoded ddp tooling so DataDesignerPlugins can serve as both NVIDIA's first-party tap and a reference shape for external tap repositories.
Usage
Repository owners configure tap metadata once in the root
pyproject.toml:Then scaffolding uses those values:
With an external tap config, the generated package, metadata, README, docs index, and import package reflect that external tap's prefix, URLs, author, and Data Designer dependency.
How
Introduces
ddp.tap_config.TapConfigplusload_tap_config()as the single shared loader for[tool.ddp.tap]. The loader validates required string fields, absolute URLs,default-source, release ref templates, and the defaultdata-designerrequirement.The config object also exposes reusable helpers for package naming, docs URLs, release refs, and source metadata so catalog/docs/source work in #17/#18 can consume the same config without adding catalog v2 output in this PR.
ddp.scaffoldnow loads tap metadata from the repo root before generating package files and exits with a clear error if the table is missing or invalid.Validation
make lintmake test-devtools(96 passed)make checkRefs #21