maoberlehner/how-to-structure-a-complex-vuex-store

This is an example project for the following article: https://markus.oberlehner.net/blog/how-to-structure-a-complex-vuex-store/

How to Structure a Complex Vuex Store

This is an example project for the following article: How to Structure a Complex Vuex Store

Build Setup

# Install dependencies.
npm install

# Serve with hot reload at localhost:8080
npm run serve

# Build for production with minification.
npm run build

About

Author

Markus Oberlehner
Website: https://markus.oberlehner.net
Twitter: https://twitter.com/MaOberlehner
PayPal.me: https://paypal.me/maoberlehner
Patreon: https://www.patreon.com/maoberlehner

License

MIT

how-to-structure-a-complex-vuex-store's Issues

Clear vuex state

If we want to clear data when our component destroyed in order we do not cache data, can we subscribe destroyed hook and call vuex action resetForm?

Or this behavior is not preferably?

persistedState

great example! really helped me. But I have a problem when I use persisted state. I want the entire state to persist over refresh. So I use the vuex-persistedState plugin - eg:
`Vue.use(Vuex)

export default new Vuex.Store({
strict: true,
plugins: [
createPersistedState()
],`

But when I do this I end with with all sorts of errors: eg.
[vuex] module namespace not found in mapGetters():

As soon as I remove the plug in all is fine - except you can't hit F5.

Any ideas?

Upgrade to Vue CLI

class to vuex module

Servus!

I have just stared using vuex, so I might not be able to implement this functionality right now.
However, I figure it might not be a big deal to generate modules from models, so why writing a module for every class manually?
Wouldn't it be more convenient to load the standard stuff via a mixin(model) and then add only module specific code?

Kind regards to LNZ,
pate