Composing events fired twice

[Anahkiasen]

I had problems with my view composers, I'm using the master branch. When I dump the fired events with a small backtrace, it seems Illuminate/View/Environment fires one, and then later one, TwigBridge fires its own. The problem View passed in the event the core Environment class fires is missing the data bound on View::make while Twig's event has those.

I double checked, I don't have any composer twice somewhere and this happen for all the views. Any idea where it might come from ?

[rcrowe]

I'll take a look at this.

I had put it in rather quickly to get the feature working for someone that requested it. The library is getting a complete reworking for 0.6.0.

[barryvdh]

This is duplicate of #59
I changed this in the loaders branch, because it required some other changes: d44d913
Don't know if there is a better way to detect if the events should be fired (perhaps listening to the events and saving the view already fired?)
In the cases I tested this, it seemed to work.

[rcrowe]

Closing in favour of #59