feat(react): dogfood native Element Rendering - #1245
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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 Element Rendering API page now offers an installed native React example alongside Angular. Three authored samples show ordered children, nested views and state-bound visibility through
RenderSpec.The caller's visibility choice survives playback, rewind, Reset and sample changes. Docs, Code and Run use the canonical route, including frontend history, reload and narrow layouts. The example runs locally without backend requests. Website e2e schedules its native build before HTTP readiness through the existing Nx prerequisites.
Validation against the actual merged Registry parent: 1,625 website unit checks, 75 registry checks and 28 native checks; strict types, three lints and ownership validation; four installed-browser checks and 726 parity checks; full production browser suite with 268 passed, four expected skips and no retries. All five Element Rendering journeys passed, and desktop/mobile screenshots were inspected. The task graph schedules fresh builds for all 19 native React previews before HTTP readiness.