react-component-queries changelog

Changelog History

• v2.3.0 Changes

  March 26, 2018

  Minor Changes

  • ✅ React v16 support + testing: fe16a81

  Patches

  • 🛠 Fix repo and homepage links: 770afc8
  • ⚡️ Updates deps and switches to prettier + eslint.: 5279a50
  • Migrates to rollup and yarn.: 8a5cd84
  • ⚡️ Updates peer deps.: 1c078f0

  Huge thanks to @evan-scott-zocdoc and @stipsan for their help!

• v2.2.0 Changes

  July 26, 2017

  🚀 Big thanks to @hoschi for this release 👏

  Minor Changes

  • Pass though sizeMe config prop 'noPlaceholder': 75fbc77

  Patches

  • 🛠 Fix mergeWith to keep 'falsy' properties from right side: 341b65e

• v2.1.3 Changes

  June 19, 2017

  Patches

  • 👮 Force react-sizeme to be at least 2.3.2: b110d04
  • ⚡️ Update to use PropTypes from prop-types package: c812f8e
  • 🛠 Fixed metadata shields: 3af28b0
  • 🔀 Merge pull request #84 from oyeanuj/patch-1: 72f81b0
  • 🔀 Merge pull request #83 from xaviervia/master: 97736ed

• v2.1.1 Changes

  September 12, 2016

  <a name"2.1.1">

  2.1.1 (2016-09-12)

  🐛 Bug Fixes

  • 🏗 build: Fixed the build. (f7c25e25)

• v2.1.0 Changes

  September 12, 2016

  <a name"2.1.0">

  2.1.0 (2016-09-12)

  🔋 Features

  • react-sizeme: Exposes new configuration option for react-sizeme. (ab0f8eca)

• v2.0.1 Changes

  September 05, 2016

  <a name"2.0.1">

  2.0.1 (2016-09-05)

  Small Changes

  • component: A static WrappedComponent prop has been added to the HOC to aid testing. Additionally the "conflictResolver" has been "moved" to the new "config" prop. The old parameter pass through method still works but can be considered deprecated. (50fbbbbb)

• v2.0.0 Changes

  September 01, 2016

  <a name"2.0.0">

  2.0.0 (2016-09-01)

  💥 Breaking Changes

  This is a partially breaking change that I don't expect will affect most users. I have extended the HOC so that it acts like a pure component. In doing so it checks to see if either the result of the queries are new or new additional props have been passed into your wrapped component. The render then only fires if one of these conditions were met. You can override this behaviour by using the new complex configuration option:
  componentQueries({ queries: [...], config: { pure: false }})
  🔧 The new config prop includes the pure option as shown above as well as all the properties from the sizeMeConfig configuration prop (which is to be deprecated).

  (1a52dfe9)