Remove DefaultApp, make DOMRenderer internal
#227
Merged
Conversation
This file contains 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
MaxDesiatov
added
documentation
carson-katri
approved these changes
Jul 31, 2020
j-f1
approved these changes
Aug 1, 2020
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.
Removes the
View-based initializer ofDOMRendererwhich no longer leaves anypublicinitializers on it, means we can make it fully internal.DOMNodeis now internal too, which is great as it was an implementation detail anyway. Corollary,DefaultAppis no longer needed.Targetwas cleaned up is it doesn't need to holdApporScenevalues, now it's just a simple protocol.I've updated
README.mdto show usage of theAppprotocol in the basic example.Closes #224.