Commits
-------

1c41a6be Removed the swiftmailer autoloading from the service provider

Discussion
----------

Removed the swiftmailer autoloading from the service provider

It is now handled by composer directly once swiftmailer/swiftmailer#212 is merged.

It is now handled by composer directly.

Commits
-------

e4641d41 made the code more readable
c89133e8 simplified some code

Discussion
----------

Code simplification

I propose to simplify some code. What do you think?

---------------------------------------------------------------------------

by stof at 2012-06-15T12:02:47Z

👍

---------------------------------------------------------------------------

by igorw at 2012-06-15T13:06:12Z

Fine with me. But please add an assignment before `setResponse` to keep the lines a bit shorter.

moved the setting of provider values after the registration to avoid having isset calls everywhere in the provider code

Before, the behavior was not consistent. Some values could be overridden
by passing an array as a second argument to the register() method, but
for most of them it did not work (we would have to wrap all definitions
with an isset()). Now, this is more consistent as you can override
everything that is defined in the provider.

If not, defining the Swiftmailer class_path after registering the
provider does not work.

moved the checks for *.class_path parameters to the boot method as people might have defined the parameter after the register method is called

Commits
-------

d53119eb added a route after middleware
794b3c28 renamed middleware() to before()

Discussion
----------

Implements route after middleware (closes #336)

This PR renames the `middleware` method to `before` and adds a new `after` route middleware.

These changes make Silex more consistent from a user point of view:

 * he can do something before the route callback on an application, a route collection, or just a route (by calling the `before` method on these objects);

 * he can do something after the route callback by calling the `after` method on an application, a route collection, or just a route.

---------------------------------------------------------------------------

by fabpot at 2012-06-13T18:20:37Z

I thought about using the `middleware` method for both before and after by passing the callback as an argument. But this has several drawback:

 * we loose the symmetry with the application before/after calls;
 * the developer must remember to manually call the callback (and symfony1 proves that many devs actually forgets about that);
 * this would act as a filter chain where the order of execution is not always clear when you have many filters.

Commits
-------

1e5d0f41 Fixed the composer constraints to have an upper bound

Discussion
----------

Fixed the composer constraints to have an upper bound

added a fat archive which contains many more Symfony component and third-party libraries (closes #365)