All Versions
85
Latest Version
Avg Release Cycle
20 days
Latest Release
744 days ago

Changelog History
Page 7

  • v0.28.0 Changes

    February 07, 2018

    ๐Ÿ†• New feature

    • โž• Added logic.withKey(params => params.id) that you can use to connect dynamic components. See this comment for more details.
  • v0.27.0 Changes

    October 25, 2017

    ๐Ÿ”„ Changed

    • โฌ†๏ธ Bigger changes to the plugin system. Please upgrade all plugins (e.g. kea-saga) to the supported versions!
    • ๐Ÿ”Œ Plugins must now be manually installed by either passing them to the plugins array in getStore, running them through activatePlugin() or importing from 'kea-plugin/install'. See the README of each plugin for details.
    • ๐Ÿ”Œ Some plugins can now also be installed just for individual logic stores, e.g. kea-localstorage.
    • ๐Ÿ’ฅ BREAKING Removed support for { persist: true } to store the output of reducers in LocalStorage. Use the kea-localstorage plugin to restore support for this feature.
    • PropTypes are no longer necessary when defining reducers.
  • v0.26.5 Changes

    October 21, 2017

    ๐Ÿ›  Fixed

    • Only mount the reducer in redux, if there's an actual reducer or a manually given path
  • v0.26.3 Changes

    October 12, 2017

    ๐Ÿ›  Fixed

    • ๐Ÿ”€ Now if you pass a wrapped component (logic(Component)) an actions prop, its conents be merged with the created actions prop.
  • v0.26.2 Changes

    October 08, 2017

    ๐Ÿ”„ Changed

    • โž• Add support for specifying your own compose enhancer in getStore(), e.g. for remote-redux-devtools
    • ๐Ÿ”จ A lot of code refactoring. The plugins API changed a bit, so upgrade your kea-saga and kea-thunk packages accordingly.
  • v0.25.0 Changes

    September 29, 2017

    ๐Ÿ”Œ Plugin support!

    • ๐Ÿ”Œ Kea now supports plugins!
    • ๐Ÿšš The previous saga functionality has moved to kea-saga. Please install it to continue using sagas!
    • ๐Ÿ”ง There's a new function, getStore, which greatly simplifies configuring your store, especially when importing plugins.

    โœ‚ Removed deprecations

    • โœ‚ Removed Logic and Scene classes and other old deprecated code. Please make sure your app works with 0.24.1 without warnings before upgrading!
  • v0.24.2 Changes

    September 17, 2017

    ๐Ÿ”„ Changed

    • ๐Ÿ‘€ Leverage action cache to enable parameterized kea logic. See #43 for more details. By @rheng
  • v0.24.1 Changes

    September 10, 2017

    ๐Ÿ”„ Changed

    • ๐Ÿ“ฆ Moved CLI tools (the kea command line utility) to separate kea-cli package
    • โž• Added "module" field to package.json with a version that uses ESnext imports instead of require calls. Should decrease bundle size by ~10kb on Webpack 2+, rollup and other module bundlers that use this
    • โž• Added a "esnext" field for people to opt in to the untranspiled source.
  • v0.23.5 Changes

    September 06, 2017

    ๐Ÿ”„ Changed & Fixed in the 0.23 series before 0.24

    • โœ‚ Remove the warning if the path is not yet conencted to Redux (needed for tests)
    • Rehydrate the store also for inline kea initializations (when the component has a key)
    • ๐Ÿ›  Fix unmounting of sagas (cancelled was not called after start stopped)
    • โž• Add connected selectors to selectors in wrapped components
    • ๐Ÿ›  Fix re-creation of empty kea({}) root selectors for shallow comparison
    • Inject proptypes to components
    • โž• Add functions to reset the store cache for tests
    • ๐Ÿ‘‰ Make sagas work with functional components
  • v0.23.0 Changes

    August 15, 2017

    ๐Ÿ†• New and old deprecations

    • โœ‚ Removed all old deprecations except for the usage of run and cancelled in sagas. These still give warnings.
    • โž• Added new deprecations for Logic and Scene classes and related code. Basically everything imported from kea/logic and kea/scene is no longer safe.
    • Saga classes and code imported from kea/saga are safe for now, but you should migrate it to the unform kea({}) syntax sooner rather than later.

    โฌ†๏ธ When upgrading, make sure your code works with 0.22.1 without any deprecation warnings. Then upgrade to 0.23.0 and remove the new warnings.