Repository navigation
Report provenance and apply write-back for compiled TypeScript views - #742
Merged
Merged
Conversation
- `native automate provenance` and `native automate edit` now work for TypeScript apps on compiled views under `native dev`. A view-reload build compiles its views with source attribution: each record names its element's file, UTF-8 byte span, line and column and the `<use>` sites that placed it, and each view lists its markup files with the hash of the bytes it was compiled from. The Debug decoder stamps this on the widget tree, so the app's provenance answers match the native markup interpreter's for the same markup, structural ids and iteration keys included. - Reloaded programs carry the same attribution, so an edit lands on the bytes on disk and the next reload reports the new bytes. The automation and TypeScript docs drop the note that write-back needs `-Dtypescript-view=false`. - Release builds, and Debug builds without view reload, are unchanged: identical core archives, contracts and exports, and identical stripped release binaries for the audited examples. A compiled-core battery compares provenance responses with the interpreter's for every widget and drives an edit from the compiled span.
|
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
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.
native automate provenanceandnative automate editnow work for TypeScript apps on compiled views undernative dev. A view-reload build compiles its views with source attribution: each record names its element's file, UTF-8 byte span, line and column and the<use>sites that placed it, and each view lists its markup files with the hash of the bytes it was compiled from. The Debug decoder stamps this on the widget tree, so the app's provenance answers match the native markup interpreter's for the same markup, structural ids and iteration keys included.-Dtypescript-view=false.