jest-haste-map: add test+fix for broken platform module support #3885
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When two platform variants of a single module ID change at the same time (ex. often happening after a far rebase), jest was loosing one of them, depending on the ordering of the change events. This is because it doesn't care about platform variants and deletes the whole module metadata every time. This is probably here for historical reasons, from before the introduction of platform extensions, and wasn't unit-tested.
This changeset adds a test and the corresponding fix for this behaviour. I wrote the test first and could see it failing if the correct fix is not added as well.