Consolidate Component API with existing code #1056
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
TimLariviere
changed the title
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.
The new Component API code was really similar to the existing
ViewAdaptercode. Both of them were running the view loop to calculate diff and apply the differences to the UI. The main difference is that ViewAdapter was only supporting the root control (eg.IFabApplication) where Component supports any control and any state management system.graph LR A[State]--changes-->B[view function] B--applies diff-->C[UI] C--triggers a change-->AI consolidated the code by removing ViewAdapter and using Component everytime.
To support non-component codebase,
UseFabulousAppwill now create an implicitComponentusing theProgrampassed to it.