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

Idea behind "Collection ID" for "Multiple Products"-Field? #2

Open
hendrik244 opened this issue Oct 21, 2022 · 0 comments
Open

Idea behind "Collection ID" for "Multiple Products"-Field? #2

hendrik244 opened this issue Oct 21, 2022 · 0 comments

Comments

@hendrik244
Copy link

hendrik244 commented Oct 21, 2022

Hi,

thanks for the plugin, first of all.
Just checked it and tried to reproduce some scenarios, which are required when you would using it for implement a custom shopify storefront with Strapi as a backend, which I did with contentful to this day.

This way i came across the option to provide a "collection id" of a collection created in shopify to automatically add/show products of this collection.

I had two thoughts about this.
By default I didn't found a way to get the id of a collection without using the api of shopify to get it.

The other is, that you have to provide the "Collection ID", when creating a new content type.
This way, for a shop with for example 4 product categories, i would have to create 4 content types, right?
For each collection. Not really best practice for this case in my opinion as I would expect to just need to create one "Product Collection" content type.

I think collection should be another shopify field type added alongside "Single Shopify Product" and "Multiple Shopify Products", where the user is able to select one of the existing collections in his shopify shop.

What do you think? Or did I maybe just misunderstood your thought, when u developed this?
Obviously I know the plugin is still in beta.

Best regards, Hendrik

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

1 participant