Evaluate inference changes in reselect due to tuple type mapping changes #50870
Labels
Needs Investigation
This issue needs a team member to investigate its status.
Needs More Info
The issue still hasn't been fully clarified
Needs Proposal
This issue needs a plan that clarifies the finer details of how it could be implemented.
In #50831, we fixed a bug around ensuring that optional tuple elements always contain a missing/undefined type, even when a mapped type tries to remove them.
However, this had some impact on 2 calls to reduxjs/reselect. Occasionally
undefined
can spoil inference results, but it's not clear where that might be taking place in the library.The text was updated successfully, but these errors were encountered: