Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How does this library differ from Veux State #26

Open
acrolink opened this issue Oct 14, 2017 · 2 comments
Open

How does this library differ from Veux State #26

acrolink opened this issue Oct 14, 2017 · 2 comments

Comments

@acrolink
Copy link

No description provided.

@juanr2001
Copy link

@acrolink , as far as I know, Vuex State help you pass data more easily without bussing or creating properties or other ugly process that makes your code very unreadable and hard to follow. When you refresh that data you stored with Vuex gets reseted to the default value. vue-cookie goal is to help you store data that is needed to persist throughout the session. Other approach you can use without using the vue-cookie is to use the vue-resource and play with the urls, like:
url/:id
and when you refresh you can fetch that :id and do something with it.

I'm sorry if I give you the wrong information. This is my best answer I can provide you.

@acrolink
Copy link
Author

@juanr2001 One limitation I had noticed with Vuex State is lack of data persistence on page navigation (between pages). As you said, using cookies solves that issue. So, would you recommend using this library to store say shopping cart items before checkout on a commerce site?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants