Open OliverJAsh opened 6 years ago
Imagine an app which has a dynamic list of counters. Users can add new counter components to a list. Each component has its own unique ID, state and reducers.
How would you handle this use case?
This is similar to cycle-onionify's makeCollection: https://github.com/staltz/cycle-onionify/tree/8b6344a749fb5b0ad7c0c8f1dcf2db4e5e1cda03#how-to-handle-a-dynamic-list-of-nested-components
makeCollection
Imagine an app which has a dynamic list of counters. Users can add new counter components to a list. Each component has its own unique ID, state and reducers.
How would you handle this use case?
This is similar to cycle-onionify's
makeCollection: https://github.com/staltz/cycle-onionify/tree/8b6344a749fb5b0ad7c0c8f1dcf2db4e5e1cda03#how-to-handle-a-dynamic-list-of-nested-components