Below you'll find all the Laravel, Composer, and the State of Autoloading articles on the site.
PHP, the language, leaves a lot to be desired when it comes to sharing and organizing your code in a project. This problem goes back to PHP's roots, and the choice not to include a python or ruby like module system. Over the years
astormToday we're going to veer slightly away from Laravel, and take a look at Composer's autoloading features. While Composer bills itself as a "Dependency Manager", its real strength is that it gives PHP developers a standard environment to build their applications in.
astormWe're jumping in mid-steam this week, so be sure to catch the first half of this article, as well as the initial article that kicked off the series.
astormThis one's a quick article to transition us from Composer back into Laravel. Also, in a rare bit of timely news, the Laravel core team just released Laravel 5.0. This release features some really big new features (a task runner!), promotion of
astormLast time we said we'd be wrapping up our series on the Laravel 4.2 autoloader. Apparently we were fibbing, because I just realized we've failed to cover a key concept in Laravel autoloading, and one that would be impossible to shoe horn into
astormPop quiz hotshot! You've put in a long day of programming. Your data models are complete, the prototype UI is done. You're going to end the day creating a simple Laravel command. You run command:make
astormLast time we finished up our look at Laravel 4.2's autoloader implementation. Like a lot of features in Laravel, (or any framework), once you pull out the microscope sharp edges begin to jut out everywhere.
astorm