// composer.json
{
"require": {
"php": ">=5.5.9",
"symfony/symfony": "3.0.*", // v3.0.0
"doctrine/orm": "~2.5@dev", // 2.7.x-dev
"doctrine/doctrine-bundle": "~1.6@dev", // 1.10.x-dev
"doctrine/doctrine-cache-bundle": "~1.2@dev", // 1.3.2
"symfony/security-acl": "~3.0@dev", // dev-master
"symfony/swiftmailer-bundle": "~2.3", // v2.3.8
"symfony/monolog-bundle": "~2.7@dev", // dev-master
"sensio/distribution-bundle": "~5.0@dev", // v5.0.22
"sensio/framework-extra-bundle": "^3.0.2", // v3.0.11
"incenteev/composer-parameter-handler": "~2.0", // v2.1.2
"doctrine/doctrine-fixtures-bundle": "^2.3", // v2.4.1
"composer/package-versions-deprecated": "^1.11" // 1.11.99
},
"require-dev": {
"sensio/generator-bundle": "~3.0", // v3.0.0
"symfony/phpunit-bridge": "~2.7" // v2.7.6
}
}
HELLLOOO Symfony3!!!
Symfony 3, ahem, Symfony 2.8, comes with a lot of sweet new stuff. Hey, we should totally take a tour through all the best stuff.
Hey Christian!
Not currently - but it's near the top of our list to add things for PhpUnit and also PhpSpec! We do already have a course on Behat, but that's functional testing :).
Cheers!
Hi,
Thanks for that nice video explaining Guard!
I wanted to redirect my users on authentication success to the page that they tried to access (if behind a firewall). Could you maybe tell me how to do that?
I'm getting lost with a lot of posts how to do that with the traditional form_login, but if I'm not mistaken, that way of handling authentication has nothing to do with the new Guard. I.e. the options for form_login in security.yml, to change the target_path etc, are not valid here, right?
Hey Carsten,
I see that inside the onAuthenticationSuccess() method you have access to the Request object, so you can fetch a referer page URL from headers like $request->headers->get('referer')
and then return a RedirectResponse to that page.
Cheers!
I noticed on fresh install of Symfony 3.0, the AsseticBundle is no more. new Symfony\Bundle\AsseticBundle\AsseticBundle(),
Do we need to install this manually now or this bundle is not going to be used any more?
Hey Shairyar!
Yea, good question - one a lot of people have been asking. The bundle is still ok to use - it's not abandoned or anything like that :). We just decided to not include it by default. If you want it, just require it and then add back the new Symfony\Bundle\AsseticBundle\AsseticBundle() line:
composer require symfony/assetic-bundle
Cheers!
Yes that's what I have done. Out of curiosity, in this series i saw a topic before that was called "Assets" I no longer see that.
Down the line, Is Symfony moving away from Assets and moving towards other tools? like Gulp or something else?
I originally planned a chapter about Assetic, but decided against it: since there's not much to cover (just that it was removed for new projects, like we're talking about). If there's any move, I think it's that Symfony is making less recommendations about assets in general. There are too many other solutions, and they all work equally well with Symfony - e.g. Gulp, etc :)
Are there any trainings for Unit Testing?