Added container with ext state option #224
Closed
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.
A pattern that we often see is that as a
ContainerHost
grows in complexity, a lot of the Container's state may exist only to track theContainerHost
's state.Essentially as we're mixing internal and external (e.g. UI) state it becomes increasingly taxing to hoist the UI state out of the container's state.
This PR introduces an optional
ContainerHostWithExtState
andContainerWithExtState
that introduce a simple mapping layer and exposeextStateFlow
for collection in the UI. We take the internal state and apply the mapper in order to turn it into an external state. All you need to do as the dev is to implement this mapper.