Repository navigation
Dogfood native React state management in the cockpit - #1242
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 state-store guide now offers a local React preview using native RenderSpec. Name, age and theme edits update authored bindings immediately while playback, rewind, Reset and sample changes preserve host state. Invalid age drafts retain the last valid value.
The example installs the existing React/core/content artifacts with a closed static presentation profile. Three samples and four read-only views exercise caller-owned state without a runtime or agent request. Docs, Code and Run share registered source assets; Angular remains the default.
Browser coverage changes host state and the selected sample before Back and Reload, then verifies the valid initial state and empty playback return. Every state-management website journey checks for runtime writes and page errors.
Fresh verification on the merged recovery source: native unit target, strict production/test types, four installed browser checks, read-only inventory validation, scoped lint with zero errors, production website build and 253 browser checks (4 expected skips, no retries). All five state-management journeys pass. The generator/proxy suite also passed 426 tests with 5 expected skips.
The previously verified broader checks remain applicable to byte-identical implementation and dependencies: all 16 installed React suites (281 checks), full registry and website unit targets (1,620 website checks), 735 parity/configuration checks, 57-app assembly and 16 actual HTTP route checks. State source comparison confirms only its baseline parent reference changed. The parent also carries the free-backend routing recovery; its deployment checks verify that integration. Desktop/mobile screenshots were reviewed during that verification.