crush losing [], {}, and undefined

[mikerowe81]

Crushing an object with empty arrays, empty objects, or undefined values results in losing the entry.

crush({ 
    arr: [],
    obj: {},
    und: undefined 
})

Current Result:

{ }

Expected Result:

{
    arr: [],
    obj: {},
    und: undefined
}

My thinking is I should be able to crush and re-construct and end up with the same object structure.

The construct function does everything except undefined

construct({ 
    arr: [],
    obj: {},
    und: undefined 
})

Current Result:

{ 
    arr: [],
    obj: {}
}

Expected Result:

{
    arr: [],
    obj: {},
    und: undefined
}

Thanks!

[aleclarson]

I believe this was intentional behavior. It seems the idea was to remove empty data structures to save on storage costs and bandwidth.

That said, it was never documented, which gives us an opportunity to make it work less surprisingly. You and I probably agree that the implied storage/bandwidth savings are not worth the lossy, unintuitive behavior that you've proposed we "fix".

Ultimately, I'd feel better treating this as a breaking change, so anyone who relies on this undocumented behavior isn't caught in the crossfire.

edit: By the way, welcome to the community, Mike! 🤝