You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a use case where I'm grouping items that may not have the keys present needed to generate a grouping key. In these cases I would actually prefer to not group them at all(vs dumping them in a catch-all bucket). I could envision other use cases where the the decision to group or not may be useful.
Current behavior appears to actually group every item with an undefined key into the same array? If so I would propose the option to discard items that have an undefinedgroupBy key.
The text was updated successfully, but these errors were encountered:
Not grouping items which have an undefined groupBy value is sensible. Unfortunately at this point changing it for everything would be a breaking change. Is the "catch-all" bucket causing a specific problem which would make it worth adding an option?
EDIT: Adding a symbol NOGROUP, which the groupBy function could return, would be a backwards compatible option which wouldn't require an option.
I have a use case where I'm grouping items that may not have the keys present needed to generate a grouping key. In these cases I would actually prefer to not group them at all(vs dumping them in a catch-all bucket). I could envision other use cases where the the decision to group or not may be useful.
Current behavior appears to actually group every item with an
undefined
key into the same array? If so I would propose the option to discard items that have anundefined
groupBy
key.The text was updated successfully, but these errors were encountered: