The last two weeks, I have tried to look at Routing a bit more indepth and have tried to suggest conventions that can help your code perform better and be easier to modify and read.
Next week, I hope to do a code walkthrough as I re-create my Laravel FAQ package to be a bit more robust, use some best practices and possibly incorporate some TDD.
Here are some highlights from the last few weeks:
Laravel Posts:
- An Easy Way To Test Eloquent Model Attributes - A look at using Jeffrey Way's L4 Test helpers to determine if model attributes exist
- Multi-TLD Routing - Supporting multiple TLDs in your L4 Route::groups
- Organizing Routes in Laravel 4 - Tips on namespacing your L4 Routes
- The Wonder of The Config Folder - An exploration of all things configurable in laravel
- Reusable Routes - Creating performant routes for local development and sudomain production
- Creating Customizable Packages With Routing - Creating customizable routing for package development
Programming and Software Architecture:
- Two Design Patterns That Will Make Your Applications Better - A look at the Repository and Gateway Patterns
- Why Method Overloading Can Signal Bad Design - Stop overloading your methods and name things better
Laravel Packages
- rtablada/eloquent-rankable - Simple model ranking algorithms for Eloquent Models
- rtablada/ordered-eloquent - Defaut orderBy on Eloquent Models (response to 2228)
- rtablada/profane - Profanity filtered Eloquent Models and general use for L4