The FiltersStore is a good place to start. It establishes a FiltersCollection that's used to manage the presentational data for filters (available options, state.) There are also refactorings to ProductStore to support merging and updating Filters as managed by collections in sprintly-data.
On the UI side, the FiltersToolbar component is created by the Items "View-Controller." All other Filter components are children of this component.
Background context
This is still WIP because there are more tests incoming.
What does it do?
Adds the filters UI and data management.
Where should the reviewer start?
The FiltersStore is a good place to start. It establishes a FiltersCollection that's used to manage the presentational data for filters (available options, state.) There are also refactorings to ProductStore to support merging and updating Filters as managed by collections in sprintly-data.
On the UI side, the
FiltersToolbar
component is created by the Items "View-Controller." All other Filter components are children of this component.Background context
This is still WIP because there are more tests incoming.
There's also likely to be a follow up PR to implement a more Flux-y pattern for reconciling dependencies between the FiltersStore and ProductStore https://docs.google.com/document/d/1zUSyoRTvRBleuU2FTvnnRqhaS-tcM1ACcabqahiOkMk/edit#
Screenshots: