Symfony 4.0 + - Track Technique eZ Roadshow 2019 - PARIS

NewinSymfony4.xFeatures to take advantage of in eZ Platform v3.x 
… and eZ Platform v2.5 for back ported features
André Rømcke
@andrerom
Nicolas Grekas
@nicolasgrekas
Expert Sponsor : Avec le support de :Roadshow Sponsor :

Some Honorable mentions
• Symfony Flex - 3.4/4.0
New, more advance way to handle projects and packages in Symfony.
• Lock Component - 3.4/4.0
Guarantee exclusive access to some shared resource. For example to ensure that a command
is not executed more than once at the same time (on the same or across different servers).
• Messenger Component - 4.1
Provides a message bus with the ability to send messages and then handle them immediately
in your application or send them through transports (e.g. queues) to be handled later on.

Symfony Maker Bundle 
Symfony Flex +Auto-wiring + Maker Bundle = ❤

$ composer req maker
$ git diff config/bundles.php
Symfony Maker Bundle

$ ./bin/console list make

$ ./bin/console make:controller DefaultController

$ vim src/Controller/DefaultController.php
src/ is about YOUR code

$ composer req twig
Adding Twig to the controller

Symfony Cache Component 
Some of the new features added in Symfony 4.x 
… and back ported to eZ Platform 2.5

New in Symfony Cache 4.2
• MarshallerInterface incl igbinary compatibility
• Multi-hosts DSN
• $cache->get($key, $callback, $beta = null)
Backported to eZ
Platform v2.5

4.2: Cache Stampede Protection at Warm-up

4.2: Cache Stampede Protection at expiry
$cache->get($key, $callback, $beta = null)
Probabilistic early expiration:
• Between not favor (0), & highly favor (INF) early expiry
•By default 1.0
• This will affect TTL on save
• Protects against lots of cache expiring at same time

New in Symfony Cache 4.3
• Optimized TagAware Redis & FileSystem adapters
• Stores tags as “relation” => Avoids tag lookups on reads
• File => Symlinks for Tags
• Redis => Redis Set datatype for tags
• Memcached? => No control over eviction of tags
Part of eZ Platform v2.5,
contributed to Symfony 4.3

[Digression] New in eZ Platform 2.5: In-Memory cache
๏ Domain specific, so not contributed to Symfony
๏ Content (Content, Location, UrlAlias) is cached for 300ms
๏ Meta data (Type, Section, User, Language) is cached for 3s
๏ In both cases limit of 100 objects & LFU to pick what to clear
In sum 2.5 has greatly improved performance!
Especially when using Redis!

Symfony HttpClient Component 
Easy too use http client, web scrapper, api consumer, ..

by @nicolasgrekas & @andrerom
composer require symfony/http-client
use SymfonyComponentHttpClientHttpClient; 
 
$client = HttpClient::create(); 
 
$url = 'https://symfony.com/versions.json'; 
$response = $client->request('GET', $url);

Consume JSON APIs in a snap
$symfonyVersions = $response->toArray(); 
 
dump($symfonyVersions); 
array:23 [ 
"lts" => "3.4.23" 
"latest" => "4.2.4" 
"dev" => "4.3.0-DEV" 
"2.0" => "2.0.25" 
"2.1" => "2.1.13" 
"2.2" => "2.2.11"
…

namespace SymfonyContractsHttpClient; 
 
// Some pieces removed to not spoil the talk 
 
interface ResponseInterface 
{ 
public function getStatusCode(): int; 
public function getHeaders(): array; 
public function getContent(): string; 
public function toArray(): array; 
}

The resiliency of the Web relies on redirects, you’re part of it
Robust and failsafe by default
/** 
* Gets the HTTP headers of the response. 
* 
* @param bool $throw Whether an exception should be thrown on 3/4/5xx status codes 
* 
* @throws TransportExceptionInterface When a network error occurs 
* @throws RedirectionExceptionInterface On a 3xx when $throw is true and the
* "max_redirects" option has been reached 
* @throws ClientExceptionInterface On a 4xx when $throw is true 
* @throws ServerExceptionInterface On a 5xx when $throw is true 
*/ 
public function getHeaders(bool $throw = true): array;
But what happens when the redirection limit is reached? or on 4xx / 5xx? Yours to decide:

Abstraction is fully decoupled
from the component
Stateless (autowired) service

Headers? Body? Options to the rescue
Options, there are a lot
of them!

Bearer? JSON payload? Options to the rescue

Optionstotherescue
'auth_basic' => null, // array|string - an array containing the username as first value, and optionally the 
// password as the second one; or string like username:password - enabling HTTP Basic 
// authentication (RFC 7617) 
'auth_bearer' => null, // string - a token enabling HTTP Bearer authorization (RFC 6750) 
'query' => [], // string[] - associative array of query string values to merge with the request's URL 
'headers' => [], // iterable|string[]|string[][] - headers names provided as keys or as part of values 
'body' => '', // array|string|resource|Traversable|Closure - the callback SHOULD yield a string 
// smaller than the amount requested as argument; the empty string signals EOF; when 
// an array is passed, it is meant as a form payload of field names and values 
'json' => null, // array|JsonSerializable - when set, implementations MUST set the "body" option to 
// the JSON-encoded value and set the "content-type" headers to a JSON-compatible 
// value it is they are not defined - typically "application/json" 
'user_data' => null, // mixed - any extra data to attach to the request (scalar, callable, object...) that 
// MUST be available via $response->getInfo('user_data') - not used internally 
'max_redirects' => 20, // int - the maximum number of redirects to follow; a value lower or equal to 0 means 
// redirects should not be followed; "Authorization" and "Cookie" headers MUST 
// NOT follow except for the initial host name 
'http_version' => null, // string - defaults to the best supported version, typically 1.1 or 2.0 
'base_uri' => null, // string - the URI to resolve relative URLs, following rules in RFC 3986, section 2 
'buffer' => true, // bool - whether the content of the response should be buffered or not 
'on_progress' => null, // callable(int $dlNow, int $dlSize, array $info) - throwing any exceptions MUST abort 
// the request; it MUST be called on DNS resolution, on arrival of headers and on 
// completion; it SHOULD be called on upload/download of data and at least 1/s 
'resolve' => [], // string[] - a map of host to IP address that SHOULD replace DNS resolution 
'proxy' => null, // string - by default, the proxy-related env vars handled by curl SHOULD be honored 
'no_proxy' => null, // string - a comma separated list of hosts that do not require a proxy to be reached 
'timeout' => null, // float - the inactivity timeout - defaults to ini_get('default_socket_timeout') 
'bindto' => '0', // string - the interface or the local socket to bind to 
'verify_peer' => true, // see https://php.net/context.ssl for the following options 
'verify_host' => true, 
'cafile' => null, 
'capath' => null, 
'local_cert' => null, 
'local_pk' => null, 
'passphrase' => null, 
'ciphers' => null, 
'peer_fingerprint' => null, 
'capture_peer_cert_chain' => false, 
'extra' => [], // array - additional options that can be ignored if unsupported, unlike regular options

• proxy – get through an HTTP proxy
• on_progress – display a progress bar / abort a request
• base_uri – resolve relative URLs / build a scoped client
• resolve – protect webhooks against calls to internal endpoints
• peer_fingerprint – pin public keys of remote certificates
• max_redirects – disable or limit redirects
Showcase of some options

• body – array|string|resource|Traversable|Closure
Options: Streameable uploads using body
$client->request('POST', 'http://upload.example.com', [ 
'body' => $mimeParts->toIterable(), // e.g. symfony/mime (in a bit) 
]);

Options: Streameable downloads
$url = 'http://releases.ubuntu.com/18.04.1/ubuntu-18.04.1-desktop-amd64.iso'; 
$response = $client->request('GET', $url, [ 
'on_progress' => 'dump', // let's spam the console for fun 
'buffer' => false, // skip buffering the response in memory 
]); 
 
// Responses are lazy! This waits only for the headers 
if (200 !== $response->getStatusCode()) { 
throw new Exception('...'); 
} 
 
$h = fopen('./ubuntu.iso', 'w'); 
foreach ($client->stream($response) as $chunk) { 
fwrite($h, $chunk->getContent()); 
}

Responses are lazy & requests are concurrent
for ($i = 0; $i < 379; ++$i) { 
$uri = "https://http2.akamai.com/demo/tile-$i.png"; 
$responses[] = $client->request('GET', $uri); 
} 
 
foreach ($responses as $response) {
// block until completion of $response
// but monitor all other responses meanwhile 
$response->getContent();
}

Asynchronous requests
for ($i = 0; $i < 379; ++$i) { 
$uri = "https://http2.akamai.com/demo/tile-$i.png"; 
$responses[] = $client->request('GET', $uri); 
} 
 
foreach ($client->stream($responses) as $response => $chunk) { 
if ($chunk->isLast()) { 
// $response completed 
} else { 
// $response's got network activity or timeout 
} 
}
• Note: $client->stream($responses, 0.0);
379 requests
completed in
0,4 s!
Max number of
seconds to wait
before yielding a
timeout chunk

Symfony Provided Clients
• NativeHttpClient – The most portable, uses PHP’s HTTP stream wrapper
• CurlHttpClient – Multiplexing, uses HTTP/2 and PUSH when available
Decorators:
• ScopingHttpClient – Auto-configure the options based on the request URL
• MockHttpClient – A client that doesn't make actual HTTP requests
• CachingHttpClient – Adds caching on top of an HTTP client
• Psr18Client – You already know about it
• with TraceableHttpClient and record & replay coming

Usage with FrameworkBundle / Autowiring
framework: 
http_client: 
max_host_connections: 4 
default_options: 
# ... 
scoped_clients: 
github_client: 
base_uri: https://api.github.com 
headers: 
Authorization: token abc123 
# creates the HttpClientInterface $githubClient autowiring alias
# and the HttpClientInterface $scopingHttpClient one

Usage with WebProfilerBundle

Usage with BrowserKitHttpBrowser
use SymfonyComponentBrowserKitHttpBrowser; 
use SymfonyComponentHttpClientHttpClient; 
 
$client = HttpClient::create(); 
$browser = new HttpBrowser($client); 
 
$browser->request('GET', 'https://example.com/'); 
$browser->clickLink('Log In'); 
$browser->submitForm('Sign In', ['username' => 'me', 'password' => 'pass']); 
$browser->clickLink('Subscriptions') 
->filter('table tr:nth-child(2) td:nth-child(2)') 
->each(function ($node) { echo trim($node->text())."n"; });

R.I.P. Goutte
HttpClient
+ DomCrawler
+ CssSelector
+ HttpKernel
+ BrowserKit

Symfony Mime Component 
Everything you need to create beautiful emails

use SymfonyComponentMimeEmail;
$email = (new Email())
->from('fabien@symfony.com')
->to('fabien@sensiolabs.com')
->subject('Some subject')
->text('Some text message')
->html('<b>Some HTML message</b>')
->attach('doc.txt')
;
The basics

Why is it so different 
from Swiftmailer?

->text('Some text message')
->html('<b>Some HTML message</b>')
;
$email = (new Swift_Message())
->setBody('Some text message')
->addPart('<b>Some HTML message</b>', 'text/html')
;
A better data object model
16k serialized
38 objects
complex serialization
"fixed" headers
2k serialized
7 objects
simple serialization
"dynamic" headers

echo $email->toString();
sleep(2);
$email->to('helene@symfony.com');
Fixed vs dynamic headers
Different 
set of headers
Date,Boundary,Message-ID

->text(fopen('email.txt', 'r'))
->html(fopen('email.html', 'r'))
;
foreach ($email->toIterable() as $chunk) {
echo $chunk;
}
String or resources,your choice

$email
->attach('Some content', 'doc.txt', 'text/plain')
->attachFromPath('/path/to/doc.txt')
->attach(fopen('doc.txt', 'r'), 'doc.txt', 'text/plain')
;
Attachments

->text('Some text')
->html('<b>The new logo: <img src="cid:logo.jpg"></b>')
->embedFromPath('logo-small.jpg', 'logo.jpg')
;
Embeds

use SymfonyBridgeTwigMimeBodyRenderer;
use SymfonyBridgeTwigMimeTemplatedEmail;
use TwigEnvironment;
use TwigLoaderFilesystemLoader;
use SymfonyComponentMimeNamedAddress;
$twig = new Environment($loader = new FilesystemLoader(__DIR__.'/templates'));
$loader->addPath(__DIR__.'/images', 'images');
$email = (new TemplatedEmail())
->to(new NamedAddress('fabien@sensiolabs.com', 'Fabien'))
->text('Some text content')
->htmlTemplate('simple.html.twig')
->context([
'city' => 'Lille'
])
;
$renderer = new BodyRenderer($twig);
$renderer->render($email);
Native integration with Twig

<p>
Welcome <b>{{ email.toName }}</b> from {{ city }}!
</p>
<p>
<img src="{{ email.image('@images/photo.jpg') }}">
</p>
SymfonyBridgeTwigMime
WrappedTemplatedEmail
Twig template name
Template context

{% do email.attach('@docs/doc.pdf') %}
<p>
Welcome <b>{{ email.toName }}</b>!
</p>
<p>
</p>

{% do email.priority(5) %}
<p>
</p>
<p>
</p>

$email = (new TemplatedEmail())
->to(new NamedAddress('fabien@sensiolabs.com', 'Fabien'))
->textTemplate('simple.txt.twig')
->htmlTemplate('simple.html.twig')
;

Tip!
If the Text part is empty,
the BodyRenderer automatically generates one

use TwigCssInlinerCssInlinerExtension;
$twig->addExtension(new CssInlinerExtension());
{% apply inline_css %}
<style>
b { color: red }
</style>
<p>
</p>
{% endapply %}
Inlining CSS

{% apply inline_css("@css/email.css") %}
<style>
b { color: red }
</style>
<p>
</p>
{% endapply %}
Inlining CSS

use TwigMarkdownMarkdownExtension;
$twig->addExtension(new MarkdownExtension());
<p>
{% apply markdown %}
| Version | LTS? | Latest |
| ------------- |:-------------:| -------:|
| 1.0 | Yes | 1.0.1 |
| 2.1 | No | 2.1.33 |
{% endapply %}
</p>
Use Markdown to simplify your templates

use TwigInkyInkyExtension;
$twig->addExtension(new InkyExtension());
Use Inky to simplify your HTML
https://foundation.zurb.com/emails.html

{% apply inky|inline_css(source("@zurb/stylesheets/main.css")) %}
<container>
<row class="header">
<columns>
<spacer size="16"></spacer>
<h4 class="text-center">Symfony Connect</h4>
</columns>
</row>
<row>
<columns>
<center><img width="100px" src="{{ email.image("@images/symfony.png") }}"></center>
<h1 class="text-center">Forgot Your Password?</h1>
<p class="text-center">It happens. Click the link below to reset it.</p>
<button class="large expand" href="#">Reset Password</button>
<hr/>
<p><small><center><a href="#">unsubscribe here</a>.</small></center></p>
</columns>
</row>
</container>
{% endapply %}
Use Inky to simplify your HTML

Symfony Mailer Component 
Everything you need to send emails

use SymfonyComponentMailerTransportSmtpSmtpTransport; 
 
$transport = new SmtpTransport('localhost');
$transport->send($email);
The basics
Email is sent for
everybody

or not at all

use SymfonyComponentMailerBridgeAmazoneSmtpSesTransport;
use SymfonyComponentMailerBridgeGoogleSmtpGmailTransport;
use SymfonyComponentMailerBridgeMailchimpSmtpMandrillTransport;
use SymfonyComponentMailerBridgeMailgunSmtpMailgunTransport;
use SymfonyComponentMailerBridgePostmarkSmtpPostmarkTransport;
use SymfonyComponentMailerBridgeSendgridSmtpSendgridTransport;
new SesTransport('user', 'pass', 'eu-west-1');
new GmailTransport('user', 'pass');
new MandrillTransport('user', 'pass');
new MailgunTransport('user', 'pass');
new PostmarkTransport(‘key');
new SendgridTransport('key');
SMTP: Shortcuts

use SymfonyComponentMailerBridgeMailgunHttpMailgunTransport;
new MailgunTransport(‘key’, ‘domain');
… also for Amazone SES & Mandrill
HTTP: Raw message

use SymfonyComponentMailerBridgeMailgunHttpApiMailgunTransport;
use SymfonyComponentMailerBridgePostmarkHttpApiPostmarkTransport;
new MailgunTransport(‘key', ‘domain');
new PostmarkTransport(‘key’);
… also for Amazone SES, Mandrill & Sendgrid
HTTP: Via API

SMTP / HTTP / API?
SMTP HTTP API
Offline Yes via Mailcatcher No / Mock No / Mock
Mailcatcher Yes No No
Standard Yes No No
Symfony generated Yes Yes No
Fast No Yes Yes

Transport::fromDsn('...');
smtp://user:pass@gmail
smtp://key@sendgrid
smtp://null
smtp://user:pass@mailgun
http://key:domain@mailgun
api://id@postmark
Use a DSN

Transport::fromDsn('...');
Failover
api://id@postmark || smtp://key@sendgrid
RoundRobin
api://id@postmark && smtp://key@sendgrid
Failover and RoundRobin transports

public function email(TransportInterface $transport)
{
$email = (new Email())->…;
return new Response('Sent');
}
Sending emails

// Under the hood this is done when async
$transport = Transport::fromDsn('smtp://localhost'));
 
$bus->dispatch($email);
Messages via Messenger

Emails are sent async via AMQP
framework:
messenger:
routing:
'SymfonyComponentMailerEnvelopedMessage': amqp
Emails are sent immediately
framework:
messenger:
routing:
#'SymfonyComponentMailerEnvelopedMessage': amqp
Sync or Async,your choice

Leverages 
the Symfony ecosystem
Twig
Encore
Serializer
Messenger
PSR logger
CSS selector
Event Dispatcher
Dependency Injection Container
Symfony Polyfills (punycode, intl, …)
… with all the great features you love in Swiftmailer 6
Symfony Mailer

Symfony 4.0 + - Track Technique eZ Roadshow 2019 - PARIS

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Symfony 4.0 + - Track Technique eZ Roadshow 2019 - PARIS

Similar to Symfony 4.0 + - Track Technique eZ Roadshow 2019 - PARIS (20)

More from eZ Systems

More from eZ Systems (20)

Recently uploaded

Recently uploaded (20)

Symfony 4.0 + - Track Technique eZ Roadshow 2019 - PARIS