Repository navigation
Prepare context for apps using dom without template. - #100
Merged
Merged
Conversation
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.
Summary
Support context scopes in existing DOM and detect duplicate Regor runtimes at import time.
Changes
createApp(context, { element })now applies:contextandr-contextwithout requiring a template:<template>content.r-ifwithin the element’s context, including hosts that also user-for.r-presubtrees untouched during preparation and binding.RegorRuntimeMismatchwhen another runtime is imported, including separate copies of the same version.1.7.5.The runtime guard detects releases containing the guard within the same JavaScript global environment.
Validation: all 593 tests pass, plus TypeScript, lint, and declaration-generation checks.