Repository navigation
feat(cockpit): dogfood native React render spec playback - #1236
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.
Render Spec’s canonical Docs, Code and Run workspace gains an installed React example at
/render/spec-rendering/react/. Three local JSON samples render through the native React Render Spec surface, with incremental playback, pause, seeking, finish and reset. Frontend history and reload create fresh playback ownership. The example runs without a backend request.The playback owner validates bounded local samples, publishes immutable projections, and fences cancelled animation frames and disposed owners. React source guidance, capability metadata and static packaging stay aligned with the canonical topic. Browser checks cover all samples, changed-state history/reload, narrow screens and zero runtime writes.
Strict docs checks exposed a hydration replay defect in Next 16.1.7’s bundled React renderer. Update Next to 16.2.12, which contains React’s merged hydration cursor fix, and add Angular/React highlighted-source copy and reload regressions. Production checks also exposed invalid mode queries retained by cached static navigation; canonical Docs query correction now uses the supported native history integration only on the current path. Other modes and cross-path replacements retain router navigation. Regression checks preserve the React selection, fragment, history length and subsequent Code/Back navigation.
Validation: all 15 installed React browser suites (277 tests); full production website (246 passed, four expected skips, no retries); development hydration/workspace repetition (28 passed, no retries); 26 workspace unit cases plus native example, website and registry unit suites; strict TypeScript; scoped lint; 119 static/profile/config contracts and 724 React parity checks; 56-example assembly and all 15 assembled React HTTP surfaces. Agent context regenerated without additional changes.
The inventory records the new dependency hashes and current main provenance; its read-only drift check and 34 inventory unit cases pass.