chore(deps): bump react-immutable-pure-component from 1.2.3 to 2.1.0

[dependabot]

Bumps react-immutable-pure-component from 1.2.3 to 2.1.0.

Release notes

Sourced from react-immutable-pure-component's releases.

v2.1.0

Change peerDependency limit

• With only string values in updateOnProps and updateOnStates no longer immutable@4 is required.

Version v2.0.1 introduced minimal immutable version to >= 4, with this release this limitation is removed. Now everything will work exactly the same way in react-immutable-pure-component@1 with immutable@<4. In case when value other then string is in updateOnProps or updateOnStates the TypeError will be thrown.

Nothing changes regarding new 'path api' for immutable >= 4

v2.0.1

Breaking changes

• No longer build as UMD, now packaged is a regular common-js module and the es6 module.
• This version is using getIn, so minimal required version of Immutable.js is now v4

New API

• We can pass paths to updateOnProps and updateOnStates which allows to be even more specific on what triggers an update. Now it viable to pass single aggregated object as a property and update only when value under specific path changes, and it works for plain js as well as immutable data structures.

class Example extends ImmutablePureComponent {
  updateOnProps = [
    ['data', 'value'],
    ['data', 'state']
  ];
  render() {...}
}

This way we don't have to split data to separate props for each child component:

items = [{ value: 'Item', status: 'new', timestamp: 123123123, lastUpdateDate: 123123123}, ...]
items.map(item => <Example data={item} />)

New example

Previous example was a little be enigmatic, this time new example allows to modify the code and explore for your self what its all about. check here

Commits

• c6cb995 Merge pull request #12 from Monar/next
• 2a7fa5b Add backwards compatibility with Immutable < 4
• 5f283ab Merge pull request #11 from Monar/next
• 4da783b Update README and set peerDependency of immutable to >= 4
• dc8af6e Setup new example
• 6cbdd82 Restructure code and init v2
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually