Taylor, we dont see any diferrense between register() and boot() functions in ServiceProvider(s). So - in 5.3 we must get first -> load all register() method for existing ServiceProviders (besides deferred) and only then call boot() methods.
It's so strange to have two methods making the same things and calling the same time.
Please, look here: link to example
@foxted agree with @arekpietrzyk oauth is just one of many authentication method and having it baked within Laravel will make it limited. Yes its an important authentication used by many application but "used by many but not used by all" doesn't imply that it needs to be implemented within the framework. Hence why application packages exists.
@Mevrael, not to start a discussion but to use 'Mail::sendConfirmationToUser($user)', I would create a seperate mailer class. It's been covered on Laracasts for sure. The way Laravel's mailer works is fine. The callbacks are easy to use. And if you don't want to use a template, you can always use 'Mail::raw()'. Good luck!
@Kostik There is a difference between boot and register. See: https://laravel.com/docs/master/providers#the-register-method for more details.
When you're logic depends on a service bound to the ioc container, you should place it in the boot method. Placing it in the register method would add the risk of the service not yet being bound to the ioc because it's service provider is loaded after the one with your logic. That explains why the first foreach loop only calls 'register()' and the the second 'boot()' :).
Y'all know you can just add an
app/Models directory and put your models in there, right?
app folder is PSR-4 namespaced, meaning that as long as you follow the naming structure (StudlyCaps folders and class names), Composer will automatically load those classes for you.