2,770 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.
I am listening to the login event, and upon receiving the event it does certain checks.
specifically, it integrates with a 3rd party service to determine if user is making a valid login. if it thinks the login is fishy, then I will either disallow the login (by logging the user out), or require the user to revalidate their email address.
so I need to be able to log a user into Laravel, have the event fire, listen for the event, then take action based on the attempted login. make sense?
Started a new Conversation How To Set Up Testing For Package Development?
I'm using the Laravel-packer by Jeroen_G. And All the tests work like a charm when there is an app.
But, when I run the tests 'inside' the package, the all break. Like:
class App\User not found. etc.
I'd like to publish the package, but the tests are key. And I need to run tests like verifying a user can login. So they can't just be unit tests. They gotta be feature tests.
What's the proper way to go about testing? Do I require Laravel for --dev?