Refactoring user vuex module

[andrzejewsky]

Related issues

closes #3095

Acceptance criteria

• network calls refactoed to data-resolvers
• independent logic moved to the helpers
• try to remove spawnNotification move the notifications one level higher (to the UI)
• replace all rootStore calls with the context instead
• remove the calls to history and me from login
• replace all fetch calls with Task api calls

Which environment this relates to

• Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
• RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
• Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

• No upgrade steps required (100% backward compatibility and no breaking changes)
• I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

Contribution and currently important rules acceptance

• I read and followed contribution rules
• I read the TypeScript Action Plan and adjusted my PR according to it
• I read about Vue Storefront Modules and I am aware that every new feature should be a module

[andrzejewsky]

Not ready yet. I'm still working on it. There are few criteria left.

[filrak]

in that cases please add WIP flag at the beginning suggesting Work in progress ;)

[filrak]

Just letting you know that name of the user cache collection will change (LS key stays the same). PR with naming change will probably be merged tomorrow. Looks good btw ;)

[pkarw]

It's on a good way - please continue and let's merge this one in shortly :)

[pkarw]

@andrzejewsky please do change the references to Vue.prototype.$db.* to StorageManager.get('*') and it should be OK to merge this one in

[andrzejewsky]

OK it's ready. I didn't remove the spawnNotification calls, Because I've noticed there is dedicated issue (https://github.com/DivanteLtd/vue-storefront/issues/3141) for that.

[patzick]

Nice work!:)
Few notes from me. Also i don't exactly get using Promise.resolve inside async methods, i asked in one of them; i'll be grateful for explanation :)

[andrzejewsky]

@patzick Done.

[filrak]

It would be nice if we could also document stuff that we write in VS docs (at least briefly). One @degi is not enough to write it, maintain it and keep up with new stuff. @andrzejewsky could you please add a Data Resolvers section to docs with very brief documentation of this one?

[andrzejewsky]

@filrak just added a new section about data resolvers in the docs, with the short example of how to create a new one

[filrak]

I meant you should document the user data resolver that you made in a new section about data resolvers in docs. Sorry if I wasn't precise. How I see this is that "data resolvers" should be a separate category in the docs with agenda more or less like:

Data resolvers

• Introduction (the doc you made)
• User data resolver
• ...

What do you think about this? ;)

[andrzejewsky]

@filrak sounds good, I'll do that.

[andrzejewsky]

@filrak Updated. Also I added docs about CategoryService. It's just a simple few words about each service. Let me know, if you have noticed there either is something missing or I should add something else.

[pkarw]

Hi @andrzejewsky is this one ready to be merged in? Have all @patzick hints from the CR been applied?

[andrzejewsky]

@pkarw yes, it's ready.

[pkarw]

OK, @andrzejewsky next time, please "Resolve" all the comments or comment about the changnes/actions taken. We're reviewing the PRs in a group of 3-4 ppl (me, @lukeromanowicz, @filrak, @patzick) and this helps us a lot :)

[patzick]

Looks good, could you just resolve conflict?