Cool animation on slides. 
Dinner break ๐ can't live-tweet ... Just listening ๐
$this->app is Container instance. Available to every ServiceProvider.
Laravel will automatically resolve the bind'ed class from Container if you ask for this in a Controller method let's say.
Laravel will automatically resolve the bind'ed class from Container if you ask for this in a Controller method let's say.
p'an p'an paam ๐
Switching to Paddle
New payment provider is added. For Paddle.
Switching to Paddle
New payment provider is added. For Paddle.
PaymentContract for all Payment Providers in the app.
Both StripePaymentProvider and PaddlePaymentProvider will implement it.
Inside controller method we will require only the contract and Laravel will return a concrete implementation.
another paymentprovider can be added too.
Both StripePaymentProvider and PaddlePaymentProvider will implement it.
Inside controller method we will require only the contract and Laravel will return a concrete implementation.
another paymentprovider can be added too.
Binding the interface to concrete implementation inside ServiceContainer is really powerful.
Laravel framework follows this pattern to provide different drivers for the same functionality, like Database.
MySQL, PgSQL and so on.
Laravel framework follows this pattern to provide different drivers for the same functionality, like Database.
MySQL, PgSQL and so on.
Why we need ServiceContainer?
Changing the control from down there to up here.
Changing the control from down there to up here.
Explicit binding and Facades.
In the back, every Facade asking for a class from Service Container.
One issue with Facade: You don't see every dependency for the class. But with constructors you can easily see dependencies for each class.
In the back, every Facade asking for a class from Service Container.
One issue with Facade: You don't see every dependency for the class. But with constructors you can easily see dependencies for each class.
Fakes are used in tests.
Let's assume we want to work with Mail.
Mail::getFacadeRoot() method returns instance of underlying class which is MailManager ( okay, i didn't know it seriously)
Mail::fake() returns different instance than MailManager.
Let's assume we want to work with Mail.
Mail::getFacadeRoot() method returns instance of underlying class which is MailManager ( okay, i didn't know it seriously)
Mail::fake() returns different instance than MailManager.
Facade::fake() calls swap() method.
Now let's fake the PaymentProvider. Woah!
Now let's fake the PaymentProvider. Woah!
PaymentFake is a custom class.
This is awesome. Make a fake class and bind it inside a fake() method on the actual class.
This is awesome. Make a fake class and bind it inside a fake() method on the actual class.
@christophrumpel uses Postmark to send transactional emails in his blog, I think?
$headers = []; //contains headers to send to Postmark
Override Laravel's base MailManager class. The overriden class can be introduced to Laravel by changing it inside MailServiceProvider.
$headers = []; //contains headers to send to Postmark
Override Laravel's base MailManager class. The overriden class can be introduced to Laravel by changing it inside MailServiceProvider.
We are able to extend the content/modify the content that's already been bind to Container. Pretty Amazing.
Singletons. Lots of ServiceProvider use it.
I think I shared this example few days ago ๐
Why we need Service Container in Laravel. It's special!
Resources to learn more about Service Container.
Course by @christophrumpel
โข โข โข
Missing some Tweet in this thread? You can try to
force a refresh
ใ
