Видео

Did you watch the first video? What are you confused about?

Not trying to be a jerk just genuinely want to answer any question you may have

everything u explained up on till the 59:30 made perfect sense, the product specific stuff part doesnt though, isn't like an $id & $upc supposed to be passed from the route or something like that, i get the route is been handled by apiResource but how does this work? and you also said adding checkProductUPC to the model, does this mean a separate method was created on the model? I'd love to get your feedback on this!

@@QuintessentialDio - Hey! Thanks for the feedback - glad to see it helped a little - I'll tell you what I am going to make a video later today for you and others as well that expands upon that - and I will directly answer all your questions - as soon as I complete it I will post the url here for you.... but to quickly answer your question --- yes you would actually get something like the product $id number in your table or what not (since products have many types of id's i don't usually just use $upc) and the $upc code from a request - like an UPDATE or READ or even a two factor delete such as delete where $id = 1 and $upc = 123 -- just to ensure some integrity ... but those would then hit your controller and in your controller that's where you're making the call to the interface - you still have to pass those arguments through as defined by your interface because that is what essentially your underlying repo & model will need to perform the operation. And that is sort of why the call it an interface (it's defining how you interface with a base class usually) Again -- its alot easier than it sounds so I'll make another video, and this would be if you wanted to further build upon and start making an actual web service based on some type of business logic you know.... I'll show you how I have mine built as well.