2,010 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.
Replied to Database Structure Of Templates
I can see two possible solutions.
I can't say which is best for your need. If the
pricing_template_values is the different for each user, the first solution is fine. Otherwise the second one will be more flexible (but also a bit more complicated to manage).
Replied to Nested Comments
Your table structure is fine. But you need a way to tell how many levels deep each comment is, in order to check if child comments are allowed. This could be done with a
getLevelAttribute accessor, which counts the number of parents.
As long as you've eager loaded all the parents, it shouldn't require any extra calls to the DB.
Replied to Multiple Form Submission Issue
You could either loop through each form, and merge their
FormData into a single object, or you could refactor the components to all be in the same
Either way, you'll have to make sure that each input has a unique name, or they will all override each other, and you'd end up with only the last form's data.
Depending on the structure, you will probably need to use array syntax for the name attributes, e.g.
<input name="forms.name"> and so forth.
If you use PhpStorm, you can run an inspection called "Declaration of overridden method should be compatible with parent class."