The open-source frontend for any eCommerce. Built with a PWA and headless approach, using a modern JS stack. We have custom integrations with Magento, commercetools, Shopware and Shopify and total coverage is just a matter of time. The API approach also allows you to merge VSF with any third-party tool like CMS, payment gateways or analytics. Newest updates: https://blog.vuestorefront.io. Always Open Source, MIT license.
From vue-storefront created by slri: vuestorefront/vue-storefront#5554
What is the motivation for adding / enhancing this feature?
Currently, working with multistore is fairly straight forward, but lacks in basic utility and, most importantly, standards. It prevents developers from having a standard way of handling specific tasks without writing their own custom code to make up for the fact that we don't have some basic functionality as a part of multistore functionality already.
What are the acceptance criteria
[ ] Utility function to pull all storeviews
[ ] Utility function to pull all storeviews extended (merge each storeview with it's parent)
[ ] Standard way of defining a default storeview *
[ ] Standard way of defining a default storeview for a domain (url field in config) **
[ ] All above utilities can be used heavily with negligible to no effect on app's performance
[ ] Documentation entries/reference for each utility
* When working with multistore there's no way of making the website render normally if we're working from localhost without us changing the host since the server compares the host from the request to urls in storeviews. This is counter productive and it also will fix my issue in yireo's local webpack without the user having to compromise core code to have the app running.
*This is a really nice to have feature, but it doesn't have to be implemented. It's just there for developers to have something to depend on when making logic based on multistore storeview configuration.*
Feel free to expand on these, I'm pretty sure I'm missing some other nice-to-haves.
Version of Vue Storefront
[x] Vue Storefront
[ ] Vue Storefront Next
Can you complete this feature request by yourself?
[ ] YES
[x] NO
Some features, if used frequently, can't just be implemented as a function in multistore.ts and left at that because frequent use will most likely result in negative effects to app's performance. I wouldn't know how to go about that in the best way specifically, so I can't complete this list myself.
From vue-storefront created by slri: vuestorefront/vue-storefront#5554
What is the motivation for adding / enhancing this feature?
Currently, working with multistore is fairly straight forward, but lacks in basic utility and, most importantly, standards. It prevents developers from having a standard way of handling specific tasks without writing their own custom code to make up for the fact that we don't have some basic functionality as a part of multistore functionality already.
What are the acceptance criteria
* When working with multistore there's no way of making the website render normally if we're working from localhost without us changing the host since the server compares the host from the request to urls in storeviews. This is counter productive and it also will fix my issue in yireo's local webpack without the user having to compromise core code to have the app running.
* This is a really nice to have feature, but it doesn't have to be implemented. It's just there for developers to have something to depend on when making logic based on multistore storeview configuration.*
Feel free to expand on these, I'm pretty sure I'm missing some other nice-to-haves.
Version of Vue Storefront
Can you complete this feature request by yourself?
Some features, if used frequently, can't just be implemented as a function in
multistore.tsand left at that because frequent use will most likely result in negative effects to app's performance. I wouldn't know how to go about that in the best way specifically, so I can't complete this list myself.