Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Build Your Framework Like Constructicons - 010PHP

Build Your Framework Like Constructicons - 010PHP

While we have a strong offering of full-stack frameworks and microframeworks, the rise of components and libraries combined with Composer allows us to easily build our own framework without reinventing the wheel. In this talk, I'll show you how the total can be more than the sum of the parts, such as Devastator was stronger than the individual Constructicons in Transformers.

Stefan Koopmanschap

May 11, 2017
Tweet

More Decks by Stefan Koopmanschap

Other Decks in Programming

Transcript

  1. View Slide

  2. BUILD YOUR FRAMEWORK
    LIKE CONSTRUCTICONS

    View Slide

  3. HI, I'M STEFAN

    View Slide

  4. HI, I'M STEFAN
    > Ingewikkeld

    View Slide

  5. HI, I'M STEFAN
    > Ingewikkeld
    > former Zend Framework translator

    View Slide

  6. HI, I'M STEFAN
    > Ingewikkeld
    > former Zend Framework translator
    > former Symfony Community Manager

    View Slide

  7. View Slide

  8. View Slide

  9. View Slide

  10. View Slide

  11. View Slide

  12. WAIT, WHAT?

    View Slide

  13. WHO HAS BUILT THEIR
    OWN FRAMEWORK?

    View Slide

  14. View Slide

  15. WHO IS STILL USING A
    CUSTOM-BUILT
    FRAMEWORK?

    View Slide

  16. View Slide

  17. THE CASE FOR A
    FRAMEWORK

    View Slide

  18. View Slide

  19. View Slide

  20. OPEN SOURCE

    View Slide

  21. SO WHY WOULD WE BUILD IT OURSELVES?

    View Slide

  22. SO WHY WOULD WE BUILD IT OURSELVES?
    > Custom needs

    View Slide

  23. SO WHY WOULD WE BUILD IT OURSELVES?
    > Custom needs
    > Because we're developers (NIH)

    View Slide

  24. SO WHY WOULD WE BUILD IT OURSELVES?
    > Custom needs
    > Because we're developers (NIH)
    > An open source framework is overkill

    View Slide

  25. SO WHY WOULD WE BUILD IT OURSELVES?
    > Custom needs
    > Because we're developers (NIH)
    > An open source framework is overkill
    > As a learning experience

    View Slide

  26. SURELY, THERE ARE MANY
    MORE REASONS

    View Slide

  27. IT IS OK TO BUILD YOUR
    OWN FRAMEWORK

    View Slide

  28. IT IS NOT OK TO WRITE
    ALL THE CODE FOR IT
    YOURSELF

    View Slide

  29. WELL, ACTUALLY...

    View Slide

  30. View Slide

  31. WRONG MOVIE

    View Slide

  32. COMPOSER

    View Slide

  33. View Slide

  34. View Slide

  35. REQUEST AND
    RESPONSE

    View Slide

  36. ROUTING

    View Slide

  37. TEMPLATING

    View Slide

  38. HANDLING
    CONFIGURATION

    View Slide

  39. SENDING E-MAIL

    View Slide

  40. DOING VALIDATION

    View Slide

  41. THE CODE

    View Slide

  42. COMPOSER INIT

    View Slide

  43. COMPOSER INIT
    {
    "name": "stefankoopmanschap/constructicons",
    "authors": [
    {
    "name": "Stefan Koopmanschap",
    "email": "[email protected]"
    }
    ],
    "require": {}
    }

    View Slide

  44. REQUEST AND RESPONSE

    View Slide

  45. REQUEST AND RESPONSE
    > react/http

    View Slide

  46. REQUEST AND RESPONSE
    > react/http
    > illuminate/http

    View Slide

  47. REQUEST AND RESPONSE
    > react/http
    > illuminate/http
    > symfony/http-foundation

    View Slide

  48. REQUEST AND RESPONSE
    composer require symfony/http-foundation

    View Slide

  49. REQUEST AND RESPONSE
    "require": {
    "symfony/http-foundation": "^3.1"
    }

    View Slide

  50. INDEX.PHP AND COMPOSER
    require(
    __DIR__ . ' /../vendor/autoload.php'
    );

    View Slide

  51. REQUEST AND RESPONSE
    use \Symfony\Component\HttpFoundation\Request;
    use \Symfony\Component\HttpFoundation\Response;
    $request = Request::createFromGlobals();
    $response = new Response(
    'Hello ' . $request->get('name', 'world')
    );
    $response->send();

    View Slide

  52. /?NAME=STEFAN
    RESULTS IN
    HELLO STEFAN

    View Slide

  53. View Slide

  54. ROUTING

    View Slide

  55. ROUTING
    > symfony/routing

    View Slide

  56. ROUTING
    > symfony/routing
    > illuminate/routing

    View Slide

  57. ROUTING
    > symfony/routing
    > illuminate/routing
    > zendframework/zend-router

    View Slide

  58. ROUTING
    > symfony/routing
    > illuminate/routing
    > zendframework/zend-router
    > nikic/fast-route

    View Slide

  59. ROUTING
    composer require nikic/fast-route

    View Slide

  60. ROUTING
    $dispatcher = FastRoute\simpleDispatcher(
    function(FastRoute\RouteCollector $r) use ($request) {
    $r->addRoute('GET', '/hello', function() use ($request) {
    $response = new Response(
    'Hello ' . $request->get('name', 'world')
    );
    $response->send();
    });
    $r->addRoute('GET', '/goodbye', function() use ($request) {
    $response = new Response(
    'Goodbye ' . $request->get('name', 'world')
    );
    $response->send();
    });
    }
    );

    View Slide

  61. ROUTING
    $dispatcher = FastRoute\simpleDispatcher(
    function(FastRoute\RouteCollector $r) use ($request) {
    // do stuff here
    }
    );

    View Slide

  62. ROUTING
    $r->addRoute('GET', '/hello', function() use ($request) {
    $response = new Response(
    'Hello ' . $request->get('name', 'world')
    );
    $response->send();
    });
    $r->addRoute('GET', '/goodbye', function() use ($request) {
    $response = new Response(
    'Goodbye ' . $request->get('name', 'world')
    );
    $response->send();
    });

    View Slide

  63. ROUTING
    $routeInfo = $dispatcher->dispatch(
    $request->getMethod(),
    $request->getRequestUri()
    );
    if (is_callable($routeInfo[1])) {
    $routeInfo[1]();
    }

    View Slide

  64. ROUTING
    $r->addRoute('GET', '/hello[/{name}]', function($params) use ($request) {
    $name = $params['name'] ?? 'world';
    $response = new Response(
    'Hello ' . $name
    );
    $response->send();
    });
    $r->addRoute('GET', '/goodbye[/{name}]', function() use ($request) {
    $name = $params['name'] ?? 'world';
    $response = new Response(
    'Goodbye ' . $name
    );
    $response->send();
    });

    View Slide

  65. ROUTING
    if (is_callable($routeInfo[1])) {
    $params = ($routeInfo[2]) ?? [];
    $routeInfo[1]($params);
    }

    View Slide

  66. View Slide

  67. TEMPLATING

    View Slide

  68. TEMPLATING
    > zetacomponents/template

    View Slide

  69. TEMPLATING
    > zetacomponents/template
    > eden/template

    View Slide

  70. TEMPLATING
    > zetacomponents/template
    > eden/template
    > twig/twig

    View Slide

  71. TEMPLATING
    composer require twig/twig

    View Slide

  72. TEMPLATING
    $twigLoader = new Twig_Loader_Filesystem(
    __DIR__ . '/../views/'
    );
    $twig = new Twig_Environment($twigLoader, [
    'cache' => '/tmp/twigCache',
    ]);

    View Slide

  73. TEMPLATING
    function(FastRoute\RouteCollector $r) use (
    $request, $twig
    ) {

    View Slide

  74. TEMPLATING
    $r->addRoute(
    'GET',
    '/hello[/{name}]',
    function($params) use ($request, $twig) {
    $name = $params['name'] ?? 'world';
    $response = new Response(
    $twig->render('hello.twig', [
    'name' => $name
    ]
    )
    );
    $response->send();
    });

    View Slide

  75. TEMPLATING
    hello.twig
    Hello {{ name }}
    goodbye.twig
    Goodbye {{ name }}

    View Slide

  76. HANDLING CONFIGURATION

    View Slide

  77. HANDLING CONFIGURATION
    > symfony/config

    View Slide

  78. HANDLING CONFIGURATION
    > symfony/config
    > illuminate/config

    View Slide

  79. HANDLING CONFIGURATION
    > symfony/config
    > illuminate/config
    > packaged/config

    View Slide

  80. HANDLING CONFIGURATION
    > symfony/config
    > illuminate/config
    > packaged/config
    > werx/config

    View Slide

  81. HANDLING CONFIGURATION
    $r->addRoute(
    'GET',
    '/contact',
    function() use ($request, $twig) {
    $response = new Response(
    $twig->render('contact.twig', [])
    );
    $response->send();
    }
    );

    View Slide

  82. HANDLING CONFIGURATION

    Your name:

    Your e-mailaddress:

    Your message:





    View Slide

  83. HANDLING CONFIGURATION
    $r->addRoute(
    'POST',
    '/contact',
    function() use ($request, $twig) {
    $mailbody = 'An e-mail was sent through the site with the following message: ' .
    $request->get('message') . "\n";
    $mailbody .= 'Sent by: ' .
    $request->get('name') .
    '<' . $request->get('email') . '>';
    mail(
    '[email protected]',
    'An e-mail from the site',
    $mailbody
    );
    $response = new \Symfony\Component\HttpFoundation\RedirectResponse('/hello');
    $response->send();
    }
    );

    View Slide

  84. HANDLING CONFIGURATION
    composer require werx/config

    View Slide

  85. HANDLING CONFIGURATION
    $configProvider = new \werx\Config\Providers\JsonProvider(
    __DIR__ . '/../config/'
    );
    $config = new \werx\Config\Container($configProvider);
    $config->load('config');

    View Slide

  86. HANDLING CONFIGURATION
    $r->addRoute(
    'POST',
    '/contact',
    function() use ($request, $config)
    {

    View Slide

  87. HANDLING CONFIGURATION
    mail(
    $config->get('contact_email'),
    'An e-mail from the site',
    $mailbody
    );

    View Slide

  88. SENDING E-MAIL

    View Slide

  89. SENDING E-MAIL
    > nette/mail

    View Slide

  90. SENDING E-MAIL
    > nette/mail
    > zetacomponents/mail

    View Slide

  91. SENDING E-MAIL
    > nette/mail
    > zetacomponents/mail
    > swiftmailer/swiftmailer

    View Slide

  92. SENDING E-MAIL
    composer require swiftmailer/swiftmailer

    View Slide

  93. SENDING E-MAIL
    $mailerTransport = Swift_SmtpTransport::newInstance(
    $config->get('mailer_server'),
    $config->get('mailer_port')
    )->setUsername($config->get('mailer_username'))
    ->setPassword($config->get('mailer_password'))
    ;
    $mailer = Swift_Mailer::newInstance($mailerTransport);

    View Slide

  94. SENDING E-MAIL
    $message = Swift_Message::newInstance('An e-mail from the site')
    ->setFrom([
    $request->get('email'),
    $request->get('name')]
    )
    ->setTo([
    $config->get('contact_email')
    ])
    ->setBody('An e-mail was sent through the site with the following message: ' .
    $request->get('message'))
    ;
    $mailer->send($message);

    View Slide

  95. DOING VALIDATION

    View Slide

  96. DOING VALIDATION
    > symfony/validator

    View Slide

  97. DOING VALIDATION
    > symfony/validator
    > zendframework/zend-validator

    View Slide

  98. DOING VALIDATION
    > symfony/validator
    > zendframework/zend-validator
    > particle/validator

    View Slide

  99. DOING VALIDATION
    composer require particle/validator

    View Slide

  100. DOING VALIDATION
    $contactMailValidator = new \Particle\Validator\Validator();
    $contactMailValidator
    ->required('name')
    ->string();
    $contactMailValidator
    ->required('email')
    ->email();
    $contactMailValidator
    ->required('message')
    ->string();

    View Slide

  101. DOING VALIDATION
    $r->addRoute(
    'POST',
    '/contact',
    function() use ($request, $config, $mailer, $contactMailValidator, $twig) {
    $result = $contactMailValidator->validate([
    'name' => $request->get('name'),
    'email' => $request->get('email'),
    'message' => $request->get('message')
    ]);
    if ($result->isValid()) {
    // send e-mail and redirect
    }
    return new Response($twig->render('contact.twig', [
    'errors' => $result->getMessages(),
    ]));
    });

    View Slide

  102. SUMMARY

    View Slide

  103. SUMMARY
    > valid use cases for building your own framework

    View Slide

  104. SUMMARY
    > valid use cases for building your own framework
    > Leverage the power of open source components and
    composer

    View Slide

  105. SUMMARY
    > valid use cases for building your own framework
    > Leverage the power of open source components and
    composer
    > Only need a few lines of glue

    View Slide

  106. SOME OTHER COMPONENTS YOU COULD THINK OF

    View Slide

  107. SOME OTHER COMPONENTS YOU COULD THINK OF
    > DI (bitexpert/disco, symfony/dependency-injection,
    league/container)

    View Slide

  108. SOME OTHER COMPONENTS YOU COULD THINK OF
    > DI (bitexpert/disco, symfony/dependency-injection,
    league/container)
    > Console (symfony/console, illuminate/console,
    webmozart/console)

    View Slide

  109. SOME OTHER COMPONENTS YOU COULD THINK OF
    > DI (bitexpert/disco, symfony/dependency-injection,
    league/container)
    > Console (symfony/console, illuminate/console,
    webmozart/console)
    > http requests (Guzzle)

    View Slide

  110. SOME OTHER COMPONENTS YOU COULD THINK OF
    > DI (bitexpert/disco, symfony/dependency-injection,
    league/container)
    > Console (symfony/console, illuminate/console,
    webmozart/console)
    > http requests (Guzzle)
    > logging (monolog/monolog)

    View Slide

  111. View Slide

  112. PHOTO CREDITS

    View Slide

  113. PHOTO CREDITS
    > Foundation by Paul Sableman, cc-by 2.0

    View Slide

  114. PHOTO CREDITS
    > Foundation by Paul Sableman, cc-by 2.0
    > Constructicon icons: James Peng

    View Slide

  115. THANK YOU!
    QUESTIONS?
    HTTP://LEFTONTHEWEB.COM
    @SKOOP
    HTTPS://JOIND.IN/TALK/79FDE

    View Slide