Add schema v2 catalog source metadata#28
Merged
eric-tramel merged 1 commit intocodex/epic-15-plugin-tapfrom May 7, 2026
Merged
Add schema v2 catalog source metadata#28eric-tramel merged 1 commit intocodex/epic-15-plugin-tapfrom
eric-tramel merged 1 commit intocodex/epic-15-plugin-tapfrom
Conversation
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
Bump the generated plugin catalog to schema version 2 and include per-entry
sourceanddocsmetadata derived from the repository tap config.This preserves the existing fields for runtime name, plugin type, description, package metadata, entry point metadata, and compatibility, including
compatibility.data_designer.requirement.Why
Schema v2 gives tap consumers enough data to show documentation links and derive install sources without importing plugin packages. The NVIDIA catalog now advertises PyPI sources by default while keeping package path as repo-local metadata.
Usage
After running
make catalog, catalog entries include the v2 additions:{ "schema_version": 2, "plugins": [ { "name": "text-transform", "source": { "type": "pypi", "package": "data-designer-template" }, "docs": { "url": "https://nvidia-nemo.github.io/DataDesignerPlugins/plugins/data-designer-template/" } } ] }How
[tool.ddp.tap]once for catalog generation and derive package-level source/docs metadata from it.[project].name.catalog/plugins.jsonand update the schema doc note now that the checked-in catalog is v2.Validation
make syncuv run pytest devtools/ddp/tests/test_catalog.py -qmake catalogmake check-catalogschema_versionand confirmedmake check-catalogfailed with exit 2, then restored and regenerated the cataloguv run ruff check devtools/ddp/src/ddp/catalog.py devtools/ddp/tests/test_catalog.pyuv run ruff format --check devtools/ddp/src/ddp/catalog.py devtools/ddp/tests/test_catalog.pymake docsmake check