|
You are here |
tomasvotruba.com | ||
| | | | |
fabien.potencier.org
|
|
| | | | | The blog of Fabien Potencier about web technology and the symfony framework | |
| | | | |
matthiasnoback.nl
|
|
| | | | | In the previous part of this series we decreased coupling of a Symfony controller to the Symfony2 framework by removing its dependency on the standard Controller class from the FrameworkBundle. Now we take a look at annotations. They were initially introduced for rapid development (no need to create/modify some configuration file, just solve the issues inline!): namespace Matthias\ClientBundle\Controller; use Sensio\Bundle\FrameworkExtraBundle\Configuration\Route; use Sensio\Bundle\FrameworkExtraBundle\Configuration\Method; use Sensio\Bundle\FrameworkExtraBundle\Configuration\Template; use Sensio\Bundle\FrameworkExtraBundle\Configuration\ParamConverter; /** * @Route("/client") */ class ClientController { /** * @Route('/{id}') * @Method("GET") * @ParamConvert... | |
| | | | |
sensiolabs.com
|
|
| | | | | Improve type safety in Symfony and Doctrine with dedicated ID classes like BookId and UserId. Avoid identifier mix-ups, enhance code clarity, and integrate better with Symfony Messenger. | |
| | | | |
blog.oestrich.org
|
|
| | | Developer blog for Eric Oestrich | ||