Explore >> Select a destination
|
You are here 
|
richardmiller.co.uk | ||
| | | | |
tomasvotruba.com
|
|
| | | | | In the previous post, we looked at [When Symfony Http Kernel is a Too Big Hammer to Use](/blog/when-symfony-http-kernel-is-too-big-hammer-to-use). We talked about the enormous content this package provides, but we don't need it. Today we'll have a little self-reflecting pause in the middle of the 4-post journey. We'll look at the main glue in Symfony Kernel - the Bundle. **Can we find a way to decompose it and use it without Kernel?** | |
| | | | |
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... | |
| | | | |
php-and-symfony.matthiasnoback.nl
|
|
| | | | | [AI summary] A detailed technical tutorial on creating and configuring custom UserProviders in Symfony2 using YAML for authentication | |
| | | | |
gist.github.com
|
|
| | | GitHub Gist: instantly share code, notes, and snippets. | ||
