[Request] View composer classes

[Anahkiasen]

Currently you can define a class as a View Composer, the problem is you can only define one class per View Composer wich clutters quickly the application with one-method files.

If would be great if you could have one class for several View Composers and then instead of having a generic compose method you could do that, just like with routes and controllers :

View::composer('myview', 'ViewComposer@myComposerMethod')

Or maybe (but that's unlikely) something that automatically parses which view to compose from the method :

View::composer('ViewComposer')

class ViewComposer
{
  public function composeView($event); // Composes the "view" View
  public function composeAnotherView($event) // Composes the "another.view" view
}

[robclancy]

Hmmm might not be a bad idea. Same could go for filters.

[franzliedke]

I like this, too. +1.

[taylorotwell]

Done on filters and composers.

[greggilbert]

Would it be possible to do the second half of what @Anahkiasen brought up? In other words, load and instantiate a view composer (e.g. View::composer('MyComposer') ) and then have it bind itself to views per method naming?