feat: align companion references with shadcn registry items#10
Merged
Conversation
Closes #5. shadcnItem now explicitly identifies the upstream schema URL, item name and registry type, hosted URL, modulora-content-v0 canonicalization, and contentSha256. It continues to reference rather than fork: install files, dependencies, CSS/env/docs, and registry dependencies remain solely in the canonical shadcn document. Define the shared web/CLI digest byte encoding in RFC 0001. Add paired conformance fixtures and cross-document validation for name/type parity, page/file target requirements, exact file digest reproduction, and meta.contentSha256 consistency. Includes mismatch and missing-target negative cases. 34/34 tests pass. Signed-off-by: Justin Levine <20596508+jal-co@users.noreply.github.com>
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
1 participant
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
Makes the shadcnItem companion reference map explicitly to the current upstream registry-item schema: schema URL, name, registry type, hosted URL, shared content canonicalization, and content digest.
Why
Closes #5. Hosted uploads need a testable cross-document contract without copying or forking shadcn's install fields.
How
Testing
34/34 tests pass, including name mismatch and registry:page missing-target failures.
Screenshots
n/a