Skip to content

Releases: neurosnap/robodux

v15.0.2

15 Sep 14:59
86c6b72
Compare
Choose a tag to compare

fix: selector memoization for loaders and tables

15 Sep 14:54
86c6b72
Compare
Choose a tag to compare

release without v prefix

20 May 21:31
c41283f
Compare
Choose a tag to compare
15.0.1

chore: use microbundle (#65)

esm and cjs support

16 Nov 00:19
c41283f
Compare
Choose a tag to compare

A new build process using https://github.com/developit/microbundle

We now support esm, cjs, and umd.

Removal of createApp and deprecated APIs

06 Apr 15:09
a0f8241
Compare
Choose a tag to compare
  • 💥 Removed createApp
  • 💥 Removed mapSlice, assignSlice, loadingSlice, loadingMapSlice.
    • Please use createTable, createAssign, createLoader, and createLoaderTable instead
  • 🔧 updated dependencies
  • 🔧 removed dependency on redux by inlining types
  • 🔧 reselect is now a dependency instead of a peerDependency

Removal of createApi

13 Jan 15:11
8467757
Compare
Choose a tag to compare

I've decided that createApi doesn't quite belong inside of robodux so I'm going to move it into its own separate repo.

I originally thought combining it with robodux would provide developers with a lot more utility. Also, since createApi leverages robodux it made sense to me at the time.

createApi is a little more experimental than I would like to have inside of robodux.

New repo: https://github.com/neurosnap/redux-express-query
npm: https://www.npmjs.com/package/redux-express-query

createApi naming changes

27 Dec 04:55
9277a10
Compare
Choose a tag to compare

Added useLoaderSuccess hook to have a callback when a loader returns success.

Changed some names around for the createPipe and createApi functions.

node v16

22 Dec 22:47
9b409a6
Compare
Choose a tag to compare

Because we are using AbortController we require node v16

createApi

22 Dec 21:26
234eeb2
Compare
Choose a tag to compare

Releasing an experimental data fetching API

Alter isInitialLoading logic

20 Jun 21:06
fcf228a
Compare
Choose a tag to compare

Previously we had faulty logic for isInitialLoading. See the commit to understand the differences.