> `reselect` is an option that you don't have to use.
Of course.
It just happens that for my real life needs I've needed state that was derived from redux state: filtering, selections, pagination, normalizing / denormalizing state, relations between entities (classic library data model problem) etc.
So I kinda can't "imagine" any "serious" work with redux without helpers like reselect etc.
> Easy to read/write once you understand the pattern.
Sure, there is nothing "complex" about any of that.
And I am genuinely asking how people deal with that.
It is just way too verbose for me. So I am wondering, how other people approach it.
Close their eyes and plow through? Don't really care?
Of course.
It just happens that for my real life needs I've needed state that was derived from redux state: filtering, selections, pagination, normalizing / denormalizing state, relations between entities (classic library data model problem) etc.
So I kinda can't "imagine" any "serious" work with redux without helpers like reselect etc.
> Easy to read/write once you understand the pattern.
Sure, there is nothing "complex" about any of that.
And I am genuinely asking how people deal with that.
It is just way too verbose for me. So I am wondering, how other people approach it.
Close their eyes and plow through? Don't really care?