chore: Remove every call to the global variable (part 2)

[DavidRouyer]

Related issues

Issue #1540
Continuation of #1613
Streamined bodybuilder version & fixed bodybuilder types

Short description and why it's useful

Screenshots of visual changes before/after (if there are any)

Screenshot of passed e2e tests (if you are using our standard setup as a backend)

(run yarn tests:e2e and paste the results. If you are not using our standard backend setup or demo.vuestorefront.io you can ommit this step)

Contribution and curently 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 refactoring plan for them

[pkarw]

@DavidRouyer won’t it be better than having rootStore.state.config.cart.synchronize_totals (violates Demeter Principle) to have just single line after toot store is imported:
config = rootStore.state.config

?

[DavidRouyer]

I'd prefer people to use the rootState and get used to it, and the store is only used to read the state, but I can change it if you want!

[pkarw]

@DavidRouyer I don't like such a long statements (i mean rootStore.state.config.<section>.<property>)

Please change it if You could and let me know when it's ready to be merged in?

[DavidRouyer]

@pkarw I've addressed your feedback, can't do better in multistore.js because prepareStoreView already contains a config parameter

[DavidRouyer]

Hm, I can't do that because I'm passing it by value and not by reference :/

[pkarw]

That’s fine. Can I merge it in?

[DavidRouyer]

I've made a lot of clean up, now the config is loaded once in app.ts. I can't use the const config = rootStore.state.config after the imports because the object is passed by value, and the initial state of the config is {}. You can use it inside the functions, but at this point it's just 💄. Please merge and change it case by case if you want to.

[pkarw]

OK,
I got it.
We can leave it as it is