Skip to content

v4.0.0
Compare
Choose a tag to compare
@github-actions github-actions released this 10 May 13:12
· 623 commits to main since this release
v4.0.0
1b4d93a

4.0.0 (2021-05-10)

Bug Fixes

  • identitygrouping: delete obsolete "hash" field from IdentityGrouping (9ae11c3)

Code Refactoring

  • remove pre-ES2017 polyfills (543e926)

Features

  • drop support for node 10 (1b4d93a)
  • first: replace "head" with "first" (51ffc0f)
  • groupbyidentitywithhash: delete groupByIdentityWithHash functions (c4b9e80)
  • keyby: change keyBy functions to return an ES2017 Map (5e594b9)
  • mapkeyby: add mapKeyBy function (4a9572e)
  • mapkeyfirstby: add mapKeyFirstBy function (2f9c825)
  • push: add push function (be3e78e)
  • shuffle: deprecate shuffle function (4238f37)
  • unqiuebyidentitywithhash: delete uniqueByIdentityWithHash functions (47657f9)
  • unshift: add unshift function (06b0e9a)
  • compile to ES2017 (8fe664e), closes #43

BREAKING CHANGES

  • identitygrouping: IdentityGrouping no longer has a "hash" field as using a hash no longer provides
    any benefit.
  • unqiuebyidentitywithhash: The uniqueByIdentityWithHash functions have been deleted. Use uniqueByIdentity
    instead. The uniqueByIdentity function now uses an ES2017 Set internally. As a result no additional
    benefit is provided by the addition of a hash function, so uniqueByIdentityWithHash is redundant.
  • groupbyidentitywithhash: The groupByIdentityWithHash functions have been deleted. Use groupByIdentity
    instead. The groupByIdentity function now uses an ES2017 Map internally. As a result no additional
    benefit is provided by the addition of a hash function, so groupByIdentityWithHash is redundant.
  • keyby: The keyBy functions now return an ES2017 Map instead of a Dictionary. The order of
    the parameterized types to these functions has also been changed to match the ordering used by Map.
  • This library now requires ES2017 API features. This breaks compatibility with Node
    < 8.10 and very old browsers that do not provide the ES2017 API. If you need to support older
    browsers then you should provide an ES2017 polyfill or continue to use v3.x of this library.
  • This library now uses ES2017 syntax. This breaks compatibility with Node < 8.10 and
    very old browsers that do not support ES2017 syntax. If you need to support older browsers, then you
    should use Babel to compile ES6+ code down to ES5.
Assets 2
Loading