axetroy / redux-zero-persist

redux-zero persist middleware

redux-zero persist middleware

Usage

const createStore = require("redux-zero")
const applyMiddleware = require("redux-zero/middleware")
const persist = require("redux-zero-persist");

const persistMiddleware = persist({ key: "[key]", storage: require("localforage") }, function(
  err,
  state
) {
  if (err) {
    console.error(err);
  } else {
    store.setState(state);
  }
});

const middlewares = applyMiddleware(
  persistMiddleware,
  antoherMiddleware
);

const store = createStore(initialState, middlewares);

Contributing

Contributing Guide

如果你觉得项目不错，不要吝啬你的 star.

长期造轮子，欢迎 follow.

Contributors

Axetroy 💻 🐛 🎨

License

redux-zero-persist's Issues

Add support for whitelist and blacklist

I'm submitting a ... (check one with "x")

• bug report => search github for a similar issue or PR before submitting
• feature request
• support request

Current behavior

Right now, we can only persist the full store, which not always will be what the user wants.

Expected behavior

I suggest we add support for a whilelist and blacklist config properties, similar to what redux-persist supports.

More detail

• Wouldn't be possible to pass both whitelist and blacklist properties, since they're contradictory - this would throw an error.
• We could rely on lodash's methods to accomplish this easily, because they allow you to pass a deep path and only return something is this path is valid.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.