<p dir="auto">Dear Fabien,<br>
Thank you for uploading your slides on the symphony hack day in Berlin.<br>
I played around with the expression language and the got the error, that in the router the request is missing.</p>
<p dir="auto">I created a fork of symfony standard to reproduce the problem:<br>
<a href="https://github.com/sebastianblum/symfony-standard/tree/routing-condition">https://github.com/sebastianblum/symfony-standard/tree/routing-condition</a></p>
<p dir="auto">If I add the condition in the routing.yml</p>
<p dir="auto">condition: "request.getMethod() in ['GET', 'POST'] and request.headers.get('User-Agent') matches '/firefox/i'"<br>
see <a href="https://github.com/sebastianblum/symfony-standard/blob/routing-condition/src/Acme/DemoBundle/Resources/config/routing.yml">https://github.com/sebastianblum/symfony-standard/blob/routing-condition/src/Acme/DemoBundle/Resources/config/routing.yml</a></p>
<p dir="auto">then I got the following error:</p>
<p dir="auto">FatalErrorException: Error: Call to a member function getMethod() on a non-object<br>
See complete stack trace <a href="https://gist.github.com/sebastianblum/7417064">https://gist.github.com/sebastianblum/7417064</a></p>
<p dir="auto">I had a problem where i put <code class="notranslate">assetic:</code> twice in <code class="notranslate">config_prod.yml</code> by accident. Because of that it didn't work as i expected. It would be nice if symfony throws a warning for this instead of just overriding/ignoring. Perhaps part of developer experience.</p>
<p dir="auto">Edit: when throwing a warning the parsing can continue</p>