As we have some changes to the TypeScript typings and I am nervous to release them in a minor release (as they have broken peoples builds in the past), I am planning to release version 4.
Currently planned features:
Help wanted:
How about adding a createNonPureSelector? https://github.com/reduxjs/reselect/issues/231#issuecomment-291155643
Maybe add createAsyncSelector #142 ?
Any progress on releasing this? I'm pretty excited
I have released 4.0.0-beta.1 to npm which addresses:
Ah yeah, I noticed that - but it was 2 months ago! What are the conditions for releasing the actual 4.0.0?
Let's have one last go at solving #340 and if we don't come up with anything satisfactory in the next week or so go ahead and release. How do people feel about the suggestion in #366 to only have the typings cover the array of input selectors?
@ellbee : my big concern with switching the order of input vs output selectors is that it's a _huge_ breaking change for Reselect. I'm not entirely against it, but there's going to be a lot of people out there who do yarn add reselect and suddenly it doesn't work the way they expect.
Yes, I 100% agree that switching the order will cause a lot of disruption. I was referring to the last paragraph, the suggestion of only having the typings cover the case where the input selectors are given in an array as the first parameter. If you are not using Typescript you shouldn't be affected at all.
Ready for the update :)
Released!
If a solution for #340 is agreed upon we'll release it in a version 5.
Reselect 4.0.0 is out, it seems like this can be closed.
Most helpful comment
Maybe add createAsyncSelector #142 ?