Skip to content

Evaluate inference changes in reselect due to tuple type mapping changes #50870

Closed
@DanielRosenwasser

Description

@DanielRosenwasser

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.

Metadata

Metadata

Labels

Needs InvestigationThis issue needs a team member to investigate its status.Needs More InfoThe issue still hasn't been fully clarifiedNeeds ProposalThis issue needs a plan that clarifies the finer details of how it could be implemented.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions