gergely
/
gergelypolonkai-web-jekyll
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
school-fallacies-post
sqla-i18n-post
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
gergelypolonkai-web-jekyll/content/blog/2013-02-27-why-i-stopped-us...

1.3 KiB
Raw Permalink Blame History Unescape Escape

Why I stopped using annotation based routing in Symfony today

date

2013-02-27T23:10:24Z

category

blog

tags

development,symfony

url

blog/2013/2/27/why-i-stopped-using-annotation-based-routing-in-symfony-today.html

save_as

blog/2013/2/27/why-i-stopped-using-annotation-based-routing-in-symfony-today.html

status

published

author

Gergely Polonkai

I have read several opinions about routing configuration in Symfony. I stayed with annotation based routing as it was convinient for me to see the URL right above the controller action. This was because by just checking the URL, I remembered the controlling code, as they always were fresh ones. Well, until today.

I had to take a look into an old (Sf 2.0, last commit was about 3 months ago) project of mine. In the same run I’ve upgraded the whole project to 2.2 (it was a fast one, thanks for JMikola@GitHub for the quick reply on my issue with JmikolaJsAssetsHelperBundle again!). After that I went on to the requested change. Now, finding a route in about 40 controller files spread between 3 bundles can really be a pain! So I’ve finished with annotation based routing. It’s still a nice feature, it’s simply not for me.