weaverryan

SymfonyCon Hack Day!

Hi! We have a mission! To make the most popular Symfony bundles (& libraries that use Symfony components) compatible with Symfony 4.

For details & instructions, see: http://symfony.com/blog/helping-prepare-for-symfony-4-bundle-support

When you create a pull request, include the text #SymfonyConHackday2017 so we can count our progress!

Also, join us on the Symfony Slack for support: http://symfony.com/slack-invite

weaverryan

<?php
// Coming in DoctrineBundle 1.8: https://github.com/doctrine/DoctrineBundle/pull/727

/* *********************
   src/Entity/CoolStuff.php
/* ********************* */
/**
 * @ORM\Entity(repositoryClass="App\Repository\CoolStuffRepository")
 */
class CoolStuff

weaverryan

<?php

namespace AppBundle\Controller;

use Symfony\Bundle\FrameworkBundle\Controller\Controller;
use Psr\Log\LoggerInterface;

/**
 * This class is now a service, so you can use normal __construct DI if you want!
 */

weaverryan

<?php
namespace AppBundle\Security;

use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\HttpFoundation\RedirectResponse;
use Symfony\Component\Security\Core\Exception\AccessDeniedException;
use Symfony\Component\Security\Http\Authorization\AccessDeniedHandlerInterface;
use Symfony\Component\Routing\RouterInterface;

class AccessDeniedHandler implements AccessDeniedHandlerInterface

weaverryan

From a user on KnpUniversity.com:

How do you manage testing form validation situations?

For form validation situations, I typically only write 2 scenarios (or sometimes just 1): one that checks that if I submit invalid data, that I see a validation error (I don’t, however assert that all of the validation errors are there – just that the form has some validation errors). Second, I write a scenario that checks a successful form submit.

For me, creating many scenarios to submit a form and check for the different validation errors is over-kill. 99% of the time, adding validation – in Symfony for example – is just one line of code. If we write a scenario for each, we now have one scenario just to test whether or not one line of code is present. For this, I check the validation errors manually – just to make sure I didn’t forget them. I’m not worried about a regression, because it’s highly unlikely that we’ll accidentally remove a line of validation and introduce a bug.

However

weaverryan

<?php

class SomeAutowiredService
{
    use UrlGeneratorTrait;
    
    public function doSomething()
    {
        $url = $this->generateUrl('homepage');
        

weaverryan

<?php

namespace AppBundle\Annotation;

/**
 * @Annotation
 * @Target("CLASS")
 */
class Link
{

weaverryan

security:
    # show the "Username not found" error message
    # yep, that easy
    hide_user_not_found: false

weaverryan

cache:
    adapters:
      my_adapter:
        type: array
        default_lifetime: 600
      other_adapter:
        type: apc

    caches:
      # creates a service cache.store_cool_stuff

weaverryan

<?php

require_once __DIR__.'/../vendor/autoload.php';

use Symfony\Component\Config\Loader\LoaderInterface;
use Symfony\Component\DependencyInjection\ContainerBuilder;
use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\HttpFoundation\Response;
use Symfony\Component\HttpKernel\MicroKernel;
use Symfony\Component\Routing\RouteCollectionBuilder;