Auto components and custom data models
Hi all, apologies if this has been asked many times before, I am still trying to learn the theory and ways to do things around here 🙂
As of right now, I am experimenting with building a custom model, trying out the auto components to represent some data with options to create/edit/delete.
- Do Auto Components such as
<AutoTable/> take in consideration the shop id?
- What is the general consensus/best practice on building a data model and frontend experience that encapsulates all functionality per shop?
- Am I right in thinking that I need to make sure I link every action's connection to a specific shop id in the crud operations, while creating custom endpoints for my frontend to call? Or is there maybe an easier way?
- There seems to be actions to crete, delete, and update but not to select. My thinking is that to all of these actions I could add some logic to filter records by shop. Is there a way to do this for retrieving data too, that could also cover the auto components functionality, maybe 😄
- Last one: I can't seem to find out how I can get the shop on the frontend! Is there a hook, or is it part of some object?2 Replies
Unknown User•11mo ago
Message Not Public
Sign In & Join Server To View
Hey @PistachioBaby thank you for the reply, this makes perfect sense!