Skip to content

State system works well for a small amount of reducers but needs more thinking #13

@Tsarpf

Description

@Tsarpf

Notes:

  • In the current system, all state reducers have to be run every time a state change occurs
    • if we knew which parts of the state a reducer is interested in, we could run them only when that part changes.
    • since the reducers are "pure" (for the lack of a better word), we know beforehand which parts of the state they're interested in --> listening to just those parts should be viable.

This is starting to sound a lot like https://github.com/Day8/re-frame

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions