6.3.0

Bugfixes

• When a request switched from a failed state to dispatched or success the reason property wasn't reset
• When a request switched from a failed state to dispatched or success the status property wasn't reset

6.2.2

Bugfixes

• correctly check whether an action belongs to kraken in reducers

6.2.1

Bugfix

• add a @@kraken/ prefix to all actions to avoid name clashes

6.2.0

Improvements

• adds a responseHeaders property to the created promise props

6.1.0

Improvements

You can now specify a new requestParams property when defining promise props. These parameters will be used to tell requests apart but won't have any influence on how kraken determines whether entities are already cached or not.

6.0.1

Fix as the 6.0.0 release didn't include the latest source build. Thank you nvm for selecting node 6.1.0 for no obvious reason!

6.0.0

Breaking changes

If you've implemented your own cache policy, you might need to update the method signature.

Old

updateRequestOnCollectionChange(
  request,
  collection
)

New

updateRequestOnCollectionChange(
  apiTypes,
  request,
  collection,
  entityType
)

v2.2.4

2.2.4