2,200 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
Earned once your experience points ranks in the top 10 of all Laracasts users.
Many thanks again, you've been superb in your explanations and taking the time to step through the process.
I'm giving you multiple 👍
@martinbean, Huge thank you!
Your explanations have been great! I do agree that using 'namespacing' is the better option.
I'm going to ask one more question based on your examples: The PostService contains what would be the traditional controller components... minus the response methods...
I found this article: https://blackdeerdev.com/laravel-services-pattern/ which matches that idea.
@martinbean thank you for the explanation.
The joy of being an educator (primarily) is that I often don't get to spend enough time developing code, so your explanation helps a great deal.
I'm used to doing the web front end + back end combined, but this need for API as well had myself, and my colleague debating best practice.
From my understanding, we put the majority of the logic in the model, returning results to both the API and WEB controllers that then handle how the data is then presented to their respective destinations.
This makes the models 'heavy' and the controllers 'light'.
The controllers could then handle the respective methods to validate requests etc.
With this in mind, creating controllers with names such as ProductsApiController and ProductsController would allow the two to be separate but relatively easy to maintain.
As for the API changes, we are attempting to have the students (and ourselves) understand how to implement APIs, so we are in a luxury situation that changes to the API are not going to affect the clients at this point and the students are very much in charge of both ends of the API loop.
Once again thanks.
@jlrdw thank you for the advice...
In this case, we need an API - or to be more precise, the students have to create an API as part of their assessable items.
We combine this with their Mobile App development so they consume the API when they implement the native app for mobile devices.
Started a new Conversation Servicing An API And Web UI From Same Laravel Installation
A fellow educator and I are wondering the best way to deal with a situation of having a Web UI and API being hosted from the same installation instance of Laravel.
We have a problem where we need an API to be served to a mobile application (to be developed), with tokens, etc, for security, plus a web UI for access from the desktop and browsers, for the administration of the application, and for general users to access the site when not on their phone/tablet.
We would like to know what the best ways are to:
We have thought of the likes of:
Is anyone able to give some guidance on the best way to structure and then implement this form of situation, and possibly a small example of a solution?
Many thanks in advance. Ady
Started a new Conversation Laravel Livewire: Returning Value From "cascaded Select" Child Component
I've followed a nice tute to give me a cascaded set of select boxes (https://talltips.novate.co.uk/livewire/dynamic-cascading-dropdown-with-livewire).
My version is used to display a list of categories, then on change of the category, show a list of icons.
What I want to be able to do, is embed this component, and receive the final selection of the item in the parent component.
I'm having problems where the icon is not getting back to the parent, and the validation is then failing.
Any direction would assist