Repository navigation
feat(react): dogfood native Registry rendering - #1244
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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 guide now offers an installed native React example alongside Angular. Three authored samples render through
RenderSpec; readers can use the complete component map, omit Badge, or supply an authored fallback, then inspect how the same JSON renders.The example preserves registry choice through playback, seek, sample changes and Reset. Docs, Code and Run use the canonical Registry route, including frontend history, reload and narrow layouts. It runs locally without backend requests. Website e2e builds the eighteenth native preview through the existing Nx prerequisites before HTTP readiness begins.
Validated against the actual Repeat merge: 1,623 website tests, 74 registry tests, 26 native tests, strict repository TypeScript checks, three scoped lint targets, ownership inventory, four installed-package browser tests, and the full production website suite (263 passed, four expected skips, no retries). Desktop and mobile native screenshots were reviewed.