v3.2.1

• fix(middleware): use global fetch as last resort #251

v3.2.0

• Add action creator for RSAA action @artursvonda - (#228)

v3.1.0

• Add support for async RSAA properties - @echolocation (#235 )
• Fixed real-world example url - @michael-freidgeim-webjet (#231)

v3.0.1

• Update dev dependencies
• Build package with non-beta versions of babel 7

v3.0.0

Breaking Changes

• The CALL_API alias has been dropped. Use RSAA (#193)
• Error handling around failed fetches has been updated (#175)
  • Previously, a failed fetch would dispatch a REQUEST FSA followed by another REQUEST FSA with an error flag
  • Now, a failed fetch will dispatch a REQUEST FSA followed by a FAILURE FSA
• Non-symbol properties are allowed on the RSAA now (#192)

Features, bug-fixes, and enhancements

• Bundling enhancements, leading to a lighter package, as well as a UMD build
• Test refactors

For more details see:

• the the 3.0 milestone
• v2.3.0...v3.0.0 for the full diff
• The upgrading from 2.x section in the readme

v2.3.0

Adds ability to pass custom fetch #174

2.2.0

• Middleware must not return a Promise on actions without RSAA properties (#167)
• Default fetch body option to undefined (#160)
• Allow [RSAA].body to be passed as a function (#168)

2.1.0

• Handle sync requests without await (#165)

v2.0.1

• Readme Updates

v2.0.0

Breaking Changes

• The CALL_API symbol is replaced with the RSAA string as the top-level RSAA action key. CALL_API is aliased to the new value as of 2.0, but this will ultimately be deprecated.
• redux-api-middleware no longer brings its own fetch implementation and depends on a global fetch to be provided in the runtime

Enhancements

• A new options config is added to pass your fetch implementation extra options other than method, headers, body and credentials

Other

See v1.0.3...v2.0.0 for the full diff.