Start to decouple dom completely from vdom #883
Merged
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.
Type: feature
The following has been addressed in the PR:
prettier
as per the readme code style guidelinesDescription:
As we start to explore other targets such as native, we need to begin decoupling the dom parts from vdom. In the future we can hopefully make vdom have some kind of agnostic "node" structure to work with, but for now that is too big of a change. So this is a small refactoring that allows the user to pass a node api (that similarly maps to the equivalent dom operations) to the mount function.
This would for instance then allow the user to write adapters for writing to something non dom like.
Down the line we'd still have these issues:
node
middleware to use the passednodeApi
but generally the same change would have to happen elsewhere