Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Demystifying React for Symfony developers
Search
Titouan Galopin
November 22, 2019
Programming
3
790
Demystifying React for Symfony developers
SymfonyCon Amsterdam 2019
Titouan Galopin
November 22, 2019
Tweet
Share
More Decks by Titouan Galopin
See All by Titouan Galopin
Concevoir son API pour le futur
tgalopin
2
1.6k
Content editing in Symfony
tgalopin
3
1k
Symfony UX: a new JavaScript ecosystem for Symfony
tgalopin
4
4.1k
[SymfonyLive Paris 2020] Pragmatic frontend for Symfony developers
tgalopin
2
1.2k
SymfonyInsight: How to setup quality processes in Symfony apps
tgalopin
2
380
Symfony 5 - AFUP Day Lille 2020
tgalopin
1
950
Pragmatic frontend for Symfony developers
tgalopin
2
1.2k
Symfony 5
tgalopin
1
700
Plongée dans l'injection de dépendances de Symfony
tgalopin
3
1.3k
Other Decks in Programming
See All in Programming
Webからモバイルへ Vue.js × Capacitor 活用事例
naokihaba
0
730
The Evolution of Enterprise Java with Jakarta EE 11 and Beyond
ivargrimstad
1
820
DroidKnights 2025 - 다양한 스크롤 뷰에서의 영상 재생
gaeun5744
3
300
Julia という言語について (FP in Julia « SIDE: F ») for 関数型まつり2025
antimon2
3
960
KotlinConf 2025 現地参加の土産話
n_takehata
0
100
都市をデータで見るってこういうこと PLATEAU属性情報入門
nokonoko1203
1
540
Javaに鉄道指向プログラミング (Railway Oriented Pro gramming) のエッセンスを取り入れる/Bringing the Essence of Railway-Oriented Programming to Java
cocet33000
2
580
事業戦略を理解してソフトウェアを設計する
masuda220
PRO
22
6.2k
Beyond Portability: Live Migration for Evolving WebAssembly Workloads
chikuwait
0
380
Elixir で IoT 開発、 Nerves なら簡単にできる!?
pojiro
1
150
GoのWebAssembly活用パターン紹介
syumai
3
10k
セキュリティマネジャー廃止とクラウドネイティブ型サンドボックス活用
kazumura
1
190
Featured
See All Featured
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
120k
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
15
1.5k
[RailsConf 2023] Rails as a piece of cake
palkan
55
5.6k
Writing Fast Ruby
sferik
628
61k
Optimising Largest Contentful Paint
csswizardry
37
3.3k
The Power of CSS Pseudo Elements
geoffreycrofte
77
5.8k
GraphQLとの向き合い方2022年版
quramy
46
14k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
233
17k
Building Adaptive Systems
keathley
43
2.6k
Fireside Chat
paigeccino
37
3.5k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
228
22k
Optimizing for Happiness
mojombo
379
70k
Transcript
Demystifying React for Symfony developers Titouan GALOPIN
2 Titouan Galopin Product Manager SymfonyInsight insight.symfony.com
Agenda 1. What’s React? 2. Components 3. Symfony integration with
Webpack Encore 3
4 1. What’s React?
5 How should we structure Javascript applications?
6 AngularJS Vue Backbone.js Dart Ember.js Dojo Meteor ...
7 There is a consensus here: MVC, or MVVM, or
MVW, ...
8 Models
9 { firstName: 'Titouan', lastName: 'Galopin', email: '
[email protected]
' }
10 Models = Observable objects
11 Bidirectional data-binding An change in the model updates the
view An change in the view updates the model
12 Two data sources Model View
13 This encourages mutations
14 { firstName: 'Tito', lastName: 'Galopin', email: '
[email protected]
' } Model
{ firstName: 'Titouan''Tito', lastName: 'Galopin', email: '
[email protected]
' } View { firstName: 'Tito' } Mutation
15 But mutations are complex
16 Complex to apply Complex to reproduce Complex to debug
17 What if we could do better?
18 The simplest way to build views is to avoid
mutations altogether
19 React does not use mutations at all
20 Instead, it has a single data source
21 Model View Observable model Two-way data flow
22 Model Observable model Two-way data flow View React One-way
data flow Model Dispatcher View
View 23 Model Observable model Two-way data flow View React
One-way data flow Model Dispatcher View
24 Model Observable model Two-way data flow View React One-way
data flow Model Dispatcher View
25 But isn’t that super slow? What about user inputs?
26 We want the benefits to blow the view away
and re-render it ... … while dealing properly with every edge cases
27 That’s React
28 React is a Javascript library for building User Interfaces
29 React is declarative render(data: array) => view: string
30 React re-renders all your view when data changes
31 2. Components
32 React’s main concept is Components
33 A component = A description of a part of
your UI that depends on your current model
34 It’s more than a template though
35 Store Dispatcher View Each component has its own model
and behavior This is component
36 The aim? Abstract away the implementation details of parts
of the UI
37
38 <Autocomplete source="/api/users" onSelect={this.handleUserSelected} />
39 <Autocomplete source="/api/users" onSelect={this.handleUserSelected} /> Property
40 But how does it work?
41 A component = A state + A way to
display that state
42 Store (Model) Dispatcher View React handles the Dispatcher and
the Store You only implement the view and define the structure of the Store
43 The state is a single Javascript object
44 The view is described by a single render() function
45 Store (state) Initial state
46 render Store (state) View (components) Initial state
47
48 class Autocomplete extends Component { constructor() { this.state =
{ results: [] }; } }
49 class Autocomplete extends Component { // ... render() {
return ( <ul> {this.state.results.map(function(result) { return ( <li>{result.name}</li> ); })} </ul> ); } }
50 class Autocomplete extends Component { // ... render() {
return ( <ul> {this.state.results.map(function(result) { return ( <li>{result.name}</li> ); })} </ul> ); } } Use of the state
51 class Autocomplete extends Component { // ... render() {
return ( <ul> {this.state.results.map(function(result) { return ( <li>{result.name}</li> ); })} </ul> ); } } Use of the state To use a property: this.props.source
State = Local data that will change over time Props
= Non-local data, read-only for the component 52
If either the state or the properties change, the component
will be re-rendered 53
54 class Autocomplete extends Component { // ... render() {
return ( <ul> {this.state.results.map(function(result) { return ( <li>{result.name}</li> ); })} </ul> ); } }
55 class Autocomplete extends Component { // ... render() {
return ( <ul> {this.state.results.map(function(result) { return ( <li>{result.name}</li> ); })} </ul> ); } } What’s that?!
56 JSX is a formatting language used by React to
express a representation of views
57 It is compiled to Javascript <li className="hello"> becomes React.DOM.li({
className: 'hello'})
58 class Autocomplete extends Component { // ... render() {
return ( <ul> {this.state.results.map(function(result) { return ( <li>{result.name}</li> ); })} </ul> ); } } Not real HTML tags but components
59 render() returns a tree of components
60 You usually create your own tree of components RegistrationForm
CityAutocompleteInput PhoneNumberInput HTMLTextInput HTMLTelInput
61 Now, how to update the view?
62 Instead of updates (mutations) React uses reconciliation
63 setState()
64 React compares the view representations and apply the changes
to the DOM
Tree of components before change Tree of components after change
setState
66 Tree of components before change Tree of components after
change setState render render View before View after
67 Tree of components before change Tree of components after
change setState render render View before View after React compares both and apply only needed changes to the DOM
68 class Autocomplete extends Component { // ... handleChange(event) {
api.fetchResults(event.target.value).then(results => { this.setState({ results: results }) }); } // ... render() { return ( <div> <input type="text" onChange={this.handleChange} /> // ... </div> ); } }
69 setState() merges the current state and the given data
...
70 … then calls recursively render() on the component and
all its children
71 render Store (state) View (components) Initial state
72 Dispatcher (React) setState render Store (state) View (components) Initial
state
73 Dispatcher (React) setState render Handled by React Store (state)
View (components) Initial state
74 Now you know React!
75 3. Symfony integration with Webpack Encore
76 Webpack is a build tool It lets you manipulate
your Javascript and CSS before using it in production (JSX, minification, …)
77 Webpack Encore wraps Webpack around a nice API to
improve its Developer Experience
78 Webpack Encore is awesome to compile React apps to
normal Javascript
79 composer req --dev webpack yarn install https://symfony.com/doc/current/frontend.html
80 yarn add @babel/preset-react react react-dom prop-types
81 // webpack.config.js const Encore = require( '@symfony/webpack-encore' ); Encore
// ... .enableReactPreset(); module.exports = Encore.getWebpackConfig();
82 Once Webpack Encore is ready, you can use it
in Twig to load React
83 // index.html.twig ... <div id="portfolio"></div> … // Output proper
<script src="..."> tags {{ encore_entry_script_tags('app') }}
84 // app.js import ReactDOM from 'react-dom'; import {App} from
'./App.js'; ReactDOM.render( <App />, document.getElementById('portfolio') );
85 // app.js import ReactDOM from 'react-dom'; import {App} from
'./App.js'; ReactDOM.render( <App />, document.getElementById('portfolio') ); Tree of components
86 And that’s all! You can now use React into
Symfony
87 Conclusion
Thanks! 88 For any question: ▪ @titouangalopin on Twitter ▪
titouan.galopin @symfony.com