Conversation
Loop handlers no longer splice item data into handler source; {expr}
is evaluated as a scoped expression instead. Update samples/docs to the
bare-expression form and add an injection regression test.
…op rendering - Add krausest-style benchmarks/ (vs React 18 + vanilla) with results in README - Fix <for>/<if>/<show> being foster-parented out of <table> by the HTML parser (escape to <template> placeholders during parsing) + real-browser e2e - Optimize loop update path: per-row binding caches, pass-scoped expression evaluator, cached handler compilation, drop O(n²) LIS from keyed diff
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.
No description provided.