Fixed namespace path
merged branch tobiassjosten/patch-1 (PR #696)

This PR was submitted for the master branch but it was merged into the 1.0 branch instead (closes #696).

Discussion
----------

Fixed namespace path

Commits
-------

044ca35 Fixed namespace path
Add target branch notes
merged branch davedevelopment/merge-wiki-into-docs (PR #699)

This PR was squashed before being merged into the 1.0 branch (closes #699).

Discussion
----------

Add target branch notes

Consolidate the information recently added to the wiki, once merged, we could edit the wiki page to point towards the docs.

Commits
-------

b99a10e Add target branch notes
reflect change: Modularity chapter renamed to Organizing Controllers (#570)
merged branch silverskater/patch-1 (PR #700)

This PR was submitted for the master branch but it was merged into the 1.0 branch instead (closes #700).

Discussion
----------

reflect change: Modularity chapter renamed to Organizing Controllers (#570)

Commits
-------

d051da3 reflect change: Modularity chapter renamed to Organizing Controllers (#570)
add '_route' key to RedirectableUrlMatcher::redirect

When there is a logger, the Symfony\Compoment\HttpKernel\EventListener\RouterListener class expects the '_route' key to exist in order to log the matched route and issues a PHP Notice
Introduced new symfony Debug component for error_handler cookbook
Workaround for OptionsResolver validating options
merged branch davedevelopment/1.0-form-test-workaround (PR #723)

This PR was squashed before being merged into the 1.0 branch (closes #723).

Discussion
----------

Workaround for OptionsResolver validating options

Couldn't think of anyway to determine which version of the form component was being used, so went with the the suck it and see.

Commits
-------

60338ac Workaround for OptionsResolver validating options
Make DoctrineServiceProvider db connection lazy
merged branch igorw/doctrine-lazy-conn (PR #722)

This PR was squashed before being merged into the 1.0 branch (closes #722).

Discussion
----------

Make DoctrineServiceProvider db connection lazy

Specifically, do not create all connections early, only create them as
needed.

Commits
-------

9cf31e4 Make DoctrineServiceProvider db connection lazy
Alter app references in middleware doc
merged branch TomAdam/pr-update-middleware-doc (PR #725)

This PR was submitted for the master branch but it was merged into the 1.0 branch instead (closes #725).

Discussion
----------

Alter app references in middleware doc

I use ControllerProvider's and functions for my controllers, and I rely on the ````Application```` and ````Request```` being injected via the parameters of each function. Today I happened to need to build some middleware, but found that ````public function before(Application $app)```` resulted in a fatal as the middleware does not use type hinting to set parameters like controllers do. On digging a bit deeper I found in ````Silex\EventListener\MiddlewareListener.php::onKernelRequest```` the following line:
````
$ret = call_user_func($callback, $request, $this->app);
````
This injects application as the second parameter. I'm really happy that it does do this, but the parameter order seems a little strange to me. It's a bit at odds with the rest of the documentation on controllers - the general method prototype is ````method(Application $app, Request $request)````. Given this, I would have expected the app to come first in the parameter list. The same applies to the after callback, except it has ````Response```` between ````Request```` and ````Application````.

The global middleware defined in ````Application```` do not inject the app in any of the callbacks, confusing the matter further. My pattern doesn't actually require this, but some people's might. Is there a reason this hasn't been done? It would be very simple to add, given the three methods are inside the ````Application```` class itself.

The ideal fix to this would be that the middleware use type hinting to apply the parameters, but this is complicated by the callbacks occurring in two classes, neither of which are local to the existing type hinting code. At the very least I think this functionality should be documented, so this is what I have provided in the PR.

Commits
-------

ddc9b92 Alter app references in middleware doc
Add note on how to handle fatal errors, as per mailing list
Fixed typo in the ServiceProviderInterface interface PHPDoc block.
merged branch hhamon/phpdoc (PR #738)

This PR was merged into the 1.0 branch.

Discussion
----------

Fixed typo in the ServiceProviderInterface interface PHPDoc block.

Commits
-------

8bf3f78 Fixed typo in the ServiceProviderInterface interface PHPDoc block.
Override the logger service by default
merged branch davedevelopment/override-logger-regardless (PR #739)

This PR was merged into the master branch.

Discussion
----------

Override the logger service by default

Fixes #731

Been sat on this for a while, not been able to think of anything else that needs doing for it.

Commits
-------

817240e Override the logger service by default
merged branch igorw/cookbook-fatal (PR #735)

This PR was merged into the 1.0 branch.

Discussion
----------

Add note on how to handle fatal errors

I'm not so happy with this solution from a usability perspective, but I don't want to have global error handlers in silex itself.

An option we could consider is making symfony's ErrorHandler fall back to an internal ``ExceptionHandler`` for fatal errors. But obviously that is not very elegant either. Ideas welcome.

Commits
-------

7a222ce Add note on how to handle fatal errors, as per mailing list