-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Reactive Collection View Controller #50
Comments
Maybe the better choice is to keep updating all views if any changes come from the upstream storage. Therefore, we should find a good mechanism to update with the minimum efforts by differentiating the changes. |
There is an additional side-effect while the storage updates cause UI refreshing. |
The collection view controller may need to track which is the current responder and re-activate it while reloading UI. |
Try to store isFirstResponder property inside the parent storage but not works properly.
|
The current implementation of collection view controller relays on the reactiveness from its storage.
But there are some potential problems need to be well-considered.
The text was updated successfully, but these errors were encountered: