You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
Looking at the documentation on Overriding and Extending I couldn't quite understand that in a situation where we need extra models, how can we have those be in relation with the respective store.
That is, lets say I have a model "Accessories", which can be linked to products from the current store. I'm assuming that we need to have something in that model that for each row in the database we can relate to the relevant store so that we can query all "Accessories" from that store for example.
Thank you!
The text was updated successfully, but these errors were encountered:
It's completely up to what you need. Would be rare to override or extend the shop model but you can definitely relate it to something. Maybe you're building a store locator and need the stores table to reference the shop in a one to many.
Oh I see, it makes sense. I was just wondering if I was missing a trait or some sort of mechanism that would treat every model in context to whatever would be the store consuming the API. Thanks for the clarification Tyler!
Looking at the documentation on Overriding and Extending I couldn't quite understand that in a situation where we need extra models, how can we have those be in relation with the respective store.
That is, lets say I have a model "Accessories", which can be linked to products from the current store. I'm assuming that we need to have something in that model that for each row in the database we can relate to the relevant store so that we can query all "Accessories" from that store for example.
Thank you!
The text was updated successfully, but these errors were encountered: