add simple test to reproduce groupBy regression #2100
Merged
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.
Hello,
While updating our codebase to the latest version of Immutable, we encountered what seems to be a regression in the behavior of
groupBy
.This change was introduced in Commit 53237d2.
Previously, grouping by a function that might return
undefined
was tolerated, but in the latest version, this now throws. While the new behavior arguably makes sense—since grouping byundefined
isn’t very clean—it does appear to be a breaking change, violating semantic versioning.If this change is considered intentional, it should also be reflected in the type system: the
grouper
function should not be allowed to returnundefined
.We’d like to clarify the intended direction:
Thanks in advance for your guidance, and thanks for maintaining the project!