MortenS

MortenS

Member Since 3 Years Ago

Experience Points
22,990
Total
Experience

2,010 experience to go until the next level!

In case you were wondering, you earn Laracasts experience when you:

  • Complete a lesson — 100pts
  • Create a forum thread — 50pts
  • Reply to a thread — 10pts
  • Leave a reply that is liked — 50pts
  • Receive a "Best Reply" award — 500pts
Lessons Completed
204
Lessons
Completed
Best Reply Awards
4
Best Reply
Awards
  • start-engines Created with Sketch.

    Start Your Engines

    Earned once you have completed your first Laracasts lesson.

  • first-thousand Created with Sketch.

    First Thousand

    Earned once you have earned your first 1000 experience points.

  • 1-year Created with Sketch.

    One Year Member

    Earned when you have been with Laracasts for 1 year.

  • 2-years Created with Sketch.

    Two Year Member

    Earned when you have been with Laracasts for 2 years.

  • 3-years Created with Sketch.

    Three Year Member

    Earned when you have been with Laracasts for 3 years.

  • 4-years Created with Sketch.

    Four Year Member

    Earned when you have been with Laracasts for 4 years.

  • 5-years Created with Sketch.

    Five Year Member

    Earned when you have been with Laracasts for 5 years.

  • school-session Created with Sketch.

    School In Session

    Earned when at least one Laracasts series has been fully completed.

  • welcome-newcomer Created with Sketch.

    Welcome To The Community

    Earned after your first post on the Laracasts forum.

  • full-time-student Created with Sketch.

    Full Time Learner

    Earned once 100 Laracasts lessons have been completed.

  • pay-it-forward Created with Sketch.

    Pay It Forward

    Earned once you receive your first "Best Reply" award on the Laracasts forum.

  • subscriber-token Created with Sketch.

    Subscriber

    Earned if you are a paying Laracasts subscriber.

  • lifer-token Created with Sketch.

    Lifer

    Earned if you have a lifetime subscription to Laracasts.

  • lara-evanghelist Created with Sketch.

    Laracasts Evangelist

    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.

  • chatty-cathy Created with Sketch.

    Chatty Cathy

    Earned once you have achieved 500 forum replies.

  • lara-veteran Created with Sketch.

    Laracasts Veteran

    Earned once your experience points passes 100,000.

  • 10k-strong Created with Sketch.

    Ten Thousand Strong

    Earned once your experience points hits 10,000.

  • lara-master Created with Sketch.

    Laracasts Master

    Earned once 1000 Laracasts lessons have been completed.

  • laracasts-tutor Created with Sketch.

    Laracasts Tutor

    Earned once your "Best Reply" award count is 100 or more.

  • laracasts-sensei Created with Sketch.

    Laracasts Sensei

    Earned once your experience points passes 1 million.

  • top-50 Created with Sketch.

    Top 50

    Earned once your experience points ranks in the top 50 of all Laracasts users.

Level 5
22,990 XP
Jun
23
4 months ago
Activity icon

Replied to Database Structure Of Templates

I can see two possible solutions.

  1. You add a user_id column to pricing_template_values.
  2. You create a pivot table to link users and pricing_template_values (many-to-many relationship).

I can't say which is best for your need. If the name in 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).

Activity icon

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.

Activity icon

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 <form>tag. 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[0].name">, <input name="forms[1].name"> and so forth.

Jun
19
4 months ago
Activity icon

Replied to Declaration Of X Should Be Compatible With Y In /path/to/file On Line Z

If you use PhpStorm, you can run an inspection called "Declaration of overridden method should be compatible with parent class."