Laravel is already a well documented system. The quick-start guide guide has all the information a developer needs to start building applications with Laravel. What's less well documented, and more interesting to me, is documentation of Laravel's implementation. The PHP community has a pretty
astorm
This week's a quick remedial primer on PHP's ArrayAccess interface. We'll be back to Laravel next time, and promise you'll see why we needed the primer.
astorm
Last time we discussed instantiating objects in Laravel using the make method. Today we're going to talk about services, service containers, and binding objects into service containers.
astorm
Subtitle: PHP Has Mysterious Ways. This week it's another quick primer on PHP's lesser known "magic" features in preparation of moving on to Laravel Facades.
astorm
So far in this series, whenever we've wanted to use a service, we've fetched Laravel's application/service-container object with the global app function
astorm
Last time we described the PHP patterns used to implement Laravel's facade feature, and started to describe some of the "gotchas" involved. We briefly discussed how a facade introduces a second type of singleton/shared service into the system, as well as the inherent problem
astorm
It's another quick primer this time. Today we're going to talk about a PHP 5.4+ feature called traits. While Laravel doesn't make heavy use of traits they are sprinkled around the core codebase, so you'll want to get familiar with them.
astorm
Another quick primer this week, but this time it's Laravel specific.
astorm
Consider the Laravel caching facade. Laravel lets you store and retrieve values to/from the cache with the following syntax
astorm
So far in this series we've stayed pretty focused on core Laravel concepts and their underlying implementation. However, this week we're going to go slightly farther afield and discuss some of the static method meta-programming used by Laravel's "Eloquent" ORM.
astorm