Repository navigation
Show component source on the page itself - #3
Merged
Merged
Conversation
The registry is copy-paste: the source is the component, so sending readers to GitHub to fetch it was the wrong shape for the page. Both files are now embedded and carry the theme's copy button. They are pulled in at build time with VitePress snippet imports from the registry vendored as a submodule, so the page cannot drift from what the registry actually holds. Checkout in CI now fetches submodules, without which the build fails.
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
This branch was successfully deployed
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.
The registry is copy-paste — the source is the component — so sending readers to GitHub to fetch it was the wrong shape for the page. Both files are now on the page, with the theme's copy button.
They are embedded at build time via VitePress snippet imports (
<<<) from the registry, vendored as a submodule atvendor/hotwire-bridge-components. The page therefore cannot drift from what the registry holds — which was my reason for linking out in the first place, now handled properly.actions/checkoutfetches submodules; the build fails without them--recurse-submodulesand bumping the pointerNote this does not address the bigger gap —
native/ios.mdis still a stub, so there is no walkthrough for building the iOS shell these components need.