-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathindex.html
1006 lines (806 loc) Β· 37.2 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Do not use FOSUserBundle</title>
<meta name="description" content="Do not (always) use FOSUserBundle - SymfonyCon 2016 conference">
<meta name="author" content="JoliCode">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<link rel="shortcut icon" href="favicon.ico">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/jolicode.css" id="theme">
<!-- Theme used for syntax highlighting of code -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<link rel="stylesheet" href="css/emojione.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement('link');
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match(/print-pdf/gi) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName('head')[0].appendChild(link);
</script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section>
<h1>Do not (always) use <span class="no-caps" style="font-size: 0.9em;">FOSUserBundle</span></h1>
<h4>And what to consider before using it</h4>
</section>
<section>
<h2>Our journey</h2>
<ol>
<li>What is FOSUserBundle
<li>Why it's not the right fit for a professional project
<li>Implementing your own User Manager
<li>Choosing a Bundle, the Right Way Β©
</ol>
</section>
<section data-state="jolistate">
<h2>Hi there! π</h2>
<ul style="float: right">
<li><a href="https://twitter.com/damienalexandre">@damienalexandre</a> π«π·</li>
<li>Symfony consultant since 2008
<li>Contributor, writer, speaker
<li>Elasticsearch π and Unicode enthusiast
<li>Beer πΊ and Bike π², not in that order
<li>First time public speaking in English π¬π§
</ul>
<p>
<a href="https://twitter.com/damienalexandre">
<img src="images/supergeek.png" alt="Me"
style="width: 20%; vertical-align: middle; background-color: white!important; padding:10px;border-radius: 15px">
</a>
</p>
</section>
<section data-state="jolistate">
<h2>I'm a consultant</h2>
<p>I do audits, developments, trainings in Paris</p>
<p>
<a href="http://jolicode.com">
<img src="./lib/font/logo-fond-noir.svg" alt="JoliCode"/>
</a>
</p>
<h3 class="no-caps">We build web and mobile apps for awesome clients.</h3>
</section>
<section data-state="jolistate">
<h2>It all started with a new project</h2>
<ul>
<li>Install Symfony and FOSUserBundle π</li>
<li>Client wants some modifications</li>
<li>Tweak the bundle</li>
<li>Rewrite part of the bundle</li>
<li>Take a step back</li>
<li>"What the hell did I do" π₯</li>
</ul>
</section>
<section data-state="jolistate">
<h2>One year ago</h2>
<p>I had to let it go:</p>
<a href="https://jolicode.com/blog/do-not-use-fosuserbundle"><img
src="images/article.png" alt="Article FOSUserBundle" style="width: 70%;"></a>
</section>
<section>
<h2 class="no-caps">Was ist FOSUserBundle?</h2>
</section>
<section>
<h2 class="no-caps">A bit of history</h2>
<ul>
<li>May, 2010: Original idea and <a
href="https://github.com/KnpLabs/KnpUserBundle/commit/3b1140f416139dd813efc9c6a02516df245f380c">first implementation</a> by KNPLabs π
<ul>
<li>Was called <strong class="emphasis">DoctrineUserBundle</strong> in reference to our good old <strong class="emphasis">sfDoctrineGuardPlugin</strong> π΄</li>
</ul>
</li>
<li>December 2010: it was <a
href="https://github.com/KnpLabs/KnpUserBundle/commit/8fbf0e9157f5f1d3be8c4ef0e380011015388ebe">moved</a> to <strong class="emphasis">FriendOfSymfony</strong>
<ul>
<li>FOS was born!</li>
</ul>
</li>
</ul>
</section>
<section>
<h2 class="no-caps">A bit of history</h2>
<p>By then you had to use Git Submodule to install bundles:</p>
<pre><code class="hljs" data-trim>git submodule add \
git://github.com/knplabs/DoctrineUserBundle.git \
src/Bundle/DoctrineUserBundle</code></pre>
<p style="font-size: 2em;">π¨</p>
</section>
<section>
<h2 class="no-caps">Symfony 2 release</h2>
<p>July 2011: Version 1.0 was tagged,<br>1 month after Symfony 2.0 release.</p>
<p>Yes we had a deps file π¬</p>
<pre><code class="hljs" data-trim>[FOSUserBundle]
git=git://github.com/FriendsOfSymfony/FOSUserBundle.git
target=bundles/FOS/UserBundle</code></pre>
</section>
<section>
<ul>
<li>πͺ 336 contributors
<li>π· 20 releases
<li>π 5β700β000 downloads
<li>π Documentation available on Symfony.com
<li>π Recommended <a href="http://symfony.com/doc/master/security/entity_provider.html">on the official documentation</a>
<li>π
Most popular on <a href="http://knpbundles.com/">KnpBundles</a>
<li>π ~5000 lines of code <small>(NCLOC: excluding the tests and comments)</small>
</ul>
</section>
<section>
<h2 class="no-caps">All the features</h2>
<ul>
<li>Provide stored User object for Symfony projects:
<ul>
<li>Doctrine ORM</li>
<li>Doctrine ODM</li>
<li>Propel (removed from 2.0, new separated bundle)</li>
</ul>
</li>
<li>Registration form with optional confirmation email
<li>Profile editing form
<li>Password reset form and handling
<li>Console commands for users management
</ul>
</section>
<section>
<h2 class="no-caps">What is not in FOSUser</h2>
<ul>
<li>Authentication (Form login, basic, LDAP...)
<li>Authorisation (Access controls...)
<li>Session management
<li>Remember Me
<li>Impersonate User
<li>Doctrine User Provider...
</ul>
</section>
<section>
<h2 class="no-caps">Two versions</h2>
<ul>
<li><strong class="emphasis">1.3.6</strong>: latest stable version <em>(1.3.7 last week)</em>
<ul>
<li>Not compatible with Symfony 3</li>
<li>54k monthly downloads <small><a href="https://packagist.org/packages/friendsofsymfony/user-bundle/downloads.json">[source]</a></small></li>
</ul>
</li>
<li><strong class="emphasis">2.0.0-alpha3</strong>: released 1 year ago <em>(beta1 2 days ago)</em>
<ul>
<li>Major update, lots of BC Break</li>
<li>24k monthly downloads</li>
</ul>
</li>
<li class="fragment"><h3 class="no-caps"><strong class="emphasis">dev-master</strong> has 135k monthly downloads π±</h3></li>
</ul>
</section>
<section>
<h2 class="no-caps">By the way</h2>
<p>Congrats <a href="https://github.com/XWB">@XWB</a> and <a href="https://github.com/stof">@stof</a> for the two releases!</p>
<h2>π</h2>
</section>
<section>
<h1 class="no-caps">Why you <br>should not<br> use it π</h1>
</section>
<section>
<h2 class="no-caps">It's an implementation, not a framework</h2>
<ul>
<li>Some choices are done for the greater good
<li>Not everything will work for you
<li>You will spend a lot of time bending the implementation to your needs
<li>This will cause some pain
</ul>
</section>
<section>
<h2 class="no-caps">Pain #1: Username and email as identifier</h2>
<ul>
<li>Login form uses <strong class="emphasis">username by default</strong> π€
<li>Both <strong class="emphasis">email</strong> and <strong class="emphasis">username</strong> are unique,
so email is also valid as identifier β
<li>Most professional websites use email as identifier
<li>You <strong class="emphasis">can't</strong> really switch to emails only π₯
</ul>
</section>
<section>
<h2 class="no-caps">Pain #1: Username and email as identifier</h2>
<p>Two user provider to chose from:</p>
<ul>
<li><code>fos_user.user_provider.username</code></li>
<li><code>fos_user.user_provider.username_email</code></li>
</ul>
</section>
<section>
<h2 class="no-caps">Pain #1: Username and email as identifier</h2>
<ul>
<li>Symfony refers to <strong class="emphasis">username</strong> everywhere:
<ul>
<li><code>UserProviderInterface::loadUserByUsername</code></li>
<li><code>UserInterface::getUsername</code></li>
</ul>
</li>
<li>It really mean "identifier", and may <a
href="https://github.com/symfony/symfony/issues/10316">change in the future</a>...</li>
<li>It's ok to have <code>getUsername</code> <a
href="http://symfony.com/doc/current/doctrine/registration_form.html#having-a-registration-form-with-only-email-no-username">return an email</a></li>
<li>But removing the username field is not possible, you have to hack!</li>
</ul>
</section>
<section>
<h2 class="no-caps">Pain #1: Bye Username</h2>
<ul>
<li>Hack the entity setter:
<pre><code class="hljs php" data-trim>public function setEmail($email) {
$email = is_null($email) ? '' : $email;
parent::setEmail($email);
$this->setUsername($email);
return $this;
}</code></pre>
</li>
<li>
Remove the field from the FormType:
<pre><code class="hljs php" data-trim>public function buildForm(FormBuilder $builder, array $options) {
parent::buildForm($builder, $options);
$builder->remove('username');
}</code></pre>
</li>
</ul>
</section>
<section>
<h2 class="no-caps">Pain #1: Bye Username</h2>
<ul>
<li>Completely rewrite the validation constraints and implement new validation groups</li>
<li>Switch the user provider to email OR username</li>
<li><a href="http://stackoverflow.com/a/21064627/665923">Full instructions here</a></li>
<li>The username field is <strong class="emphasis">still in the database</strong> π‘</li>
</ul>
</section>
<section>
<h2 class="no-caps">Pain #1: username_email provider is a hack β </h2>
<pre><code style="font-size: 1.2em;" class="hljs php" data-trim>public function findUserByUsernameOrEmail($usernameOrEmail)
{
if (preg_match('/^.+\@\S+\.\S+$/', $usernameOrEmail)) {
return $this->findUserByEmail($usernameOrEmail);
}
return $this->findUserByUsername($usernameOrEmail);
}</code></pre>
<p>Creative usernames will never be found:<br /> <strong class="emphasis">[@lpha.org]</strong>, <strong class="emphasis">π @3.14</strong>...</p>
</section>
<section>
<h2 class="no-caps">Pain #2: Database</h2>
<p>The default table is full of fields you may never use <br>and π« cannot be removed π«</p>
<ul>
<li><code>username</code> and <code>username_canonical</code></li>
<li><code>email_canonical</code> β </li>
<li><code>salt</code>, not needed since bcrypt (UserInterface)</li>
<li><code>last_login</code>, an UPDATE on each login β </li>
<li><code>roles</code> is <code>(DC2Type:array)</code>, no interoperability</li>
</ul>
</section>
<section>
<h2 class="no-caps">Pain #2: Database</h2>
<ul>
<li><strong class="emphasis">AdvancedUserInterface</strong> is implemented π
<ul>
<li><code>locked</code></li>
<li><del><code>expired</code></del></li>
<li><code>expires_at</code></li>
<li><del><code>credentials_expired</code></del></li>
<li><code>credentials_expire_at</code></li>
</ul>
</li>
<li>Doctrine's <strong class="emphasis">AttributeOverrides</strong> may allow to edit some fields options,
but no removing or type switching.</li>
</ul>
</section>
<section>
<h2 class="no-caps">Pain #3: Wording</h2>
<p>Obviously default template <strong class="emphasis">must</strong> be customized π¨</p>
<img src="images/fosuser-default-register.png" alt="Register FOSUserBundle">
</section>
<section>
<h2 class="no-caps">Pain #3: Wording</h2>
<ul>
<li>Setting your own layout:<br>
<code>app/Resources/FOSUserBundle/views/layout.html.twig</code>
</li>
<li>Special block <strong class="emphasis">fos_user_content</strong>:
<pre><code class="hljs twig" data-trim>{% extends "::base.html.twig" %}
{% block body %}
{% block fos_user_content %}{% endblock fos_user_content %}
{{ parent() }}
{% endblock body %}</code></pre>
</li>
<li>You <strong class="emphasis">HAVE</strong> to display flash messages</li>
</ul>
</section>
<section>
<h2 class="no-caps">Pain #3: Wording</h2>
<img src="images/fosuser-register-custom.png" alt="FOSUserBundle register nice">
</section>
<section>
<h2 class="no-caps">Pain #3: Wording</h2>
<blockquote>The user has been created successfully</blockquote>
<p style="font-size: 2em;">π π€</p>
</section>
<section>
<h2 class="no-caps">Pain #3: Wording</h2>
<ul>
<li><strong class="emphasis">Good:</strong> All the texts are provided and translated in 40 languages π thanks to awesome contributors π</li>
<li><strong class="emphasis">Bad:</strong> Messages are very generics, so you still have some translation work to do β</li>
</ul>
</section>
<section>
<h2 class="no-caps">Pain #3: Wording</h2>
<p><code>app/Resources/translations/FOSUserBundle.en.yml</code></p>
<pre><code class="hljs yaml" data-trim>registration:
flash:
user_created: >
Your account has been created successfully,
congratulation!</code></pre>
</section>
<section>
<h2 class="no-caps">Pain #3: Wording</h2>
<ul>
<li>Emails are Twig files with translations, <br>and only the <strong class="emphasis">txt part</strong> is provided</li>
<li>The Mailer use Twig blocks to get the subject, text and html body parts</li>
<li>There is a MailerInterface, because the default one is opinionated</li>
<li class="fragment">I often build a custom FOSUser Mailer as bridge to my real application Mailer π</li>
</ul>
</section>
<section>
<h2 class="no-caps">Pain #4: Extendability</h2>
<ul>
<li>Adding a field to the user profile is easy, it's your entity:
<pre><code class="hljs php" data-trim>/**
* @var \DateTime
* @ORM\Column(name="birth_date", type="date")
* @Assert\LessThan("-13 years", groups={"Registration", "Profile"})
*/
protected $birthDate;</code></pre>
</li>
<li><strong class="emphasis">DO NOT</strong> forget the validation groups if you need validation</li>
<li>What about form types then?</li>
</ul>
</section>
<section>
<h2 class="no-caps">Pain #4: Extendability</h2>
<pre><code class="hljs php" data-trim>class RegistrationType extends AbstractType
{
public function buildForm(FormBuilderInterface $builder, array $options)
{
$builder->add('birthDate');
}
// Extends the bundle form type
public function getParent()
{
return RegistrationFormType::class;
}
}</code></pre>
</section>
<section>
<h2 class="no-caps">Pain #4: Extendability</h2>
<pre><code class="hljs yaml" data-trim>fos_user:
...
registration:
form:
type: "AppBundle\Form\RegistrationType"
</code></pre>
<p>To do for both the registration and profile types π</p>
</section>
<section>
<h2 class="no-caps">File madness π¨</h2>
<pre style="font-size: 0.4em; float:left; width: 55%; margin-right: 10px;"><code class="hljs" data-trim>app/Resources
βββ FOSUserBundle
β βββ views
β βββ Registration
β β βββ email.txt.twig
β β βββ confirmed.html.twig
β β βββ check_email.html.twig
β β βββ register_content.html.twig
β βββ Resetting
β β βββ check_email.html.twig
β β βββ request.html.twig
β β βββ reset.html.twig
β βββ Security
β βββ login.html.twig
βββ translations
βββ FOSUserBundle.en.yml
βββ validators.en.yml
</code></pre>
<pre style="font-size: 0.4em;float: left;width: auto;"><code class="hljs" data-trim>src/
βββ AppBundle
βββ Form
βΒ Β βββ RegistrationType.php
βΒ Β βββ ProfileType.php
βββ Manager
Β Β βββ FOSUserEmail.php
</code></pre>
</section>
<section>
<h2 class="no-caps">So much files and overwriting</h2>
<p>
Very soon in your projects, you will note that<br> <strong class="emphasis">you are building a lot on top of the Bundle</strong>,
increasing your dependency on it.
</p>
<p>That's called Technical Debt.</p>
<p class="fragment">
Why not drop the bundle and write them anyway? π€
</p>
</section>
<section>
<h2 class="no-caps">π₯ Bonus pain π₯</h2>
</section>
<section>
<h2 class="no-caps">Separated User entities</h2>
<ul>
<li>You need a <strong class="emphasis">Customer</strong> entity and an <strong class="emphasis">Admin</strong> entity?</li>
<li class="fragment">Install PUGXMultiUserBundle (ORM only), a Bundle that extends FOSUserBundle!</li>
<li class="fragment">π¨ At your own risks π¨</li>
</ul>
</section>
<section>
<h2 class="no-caps">Separated Login Forms</h2>
<ul>
<li>Custom login form for backend and customer access?
<ul class="fragment">
<li>custom routes for everything</li>
<li>a new firewall and new <code>access_control</code> entries
<li>a new <code>SecurityController</code> extending the bundle one,
with some conditions to know what template to render π
<li>and of course the new template</li>
</ul>
</li>
</ul>
</section>
<section>
<h2 class="no-caps">Why you shouldn't use it</h2>
<ul>
<li>Technical debt generator if you need customization
<li>Hard to adapt, lots of file to write
<li>Hardly maintained π§ <em>(maybe not anymore)</em>
<li>Makes visible your usage of Symfony + FOSUserBundle, which can be a security concern π΅</li>
</ul>
<blockquote>inurl:"/resetting/request" "Username or email address"</blockquote>
</section>
<section>
<h2 class="no-caps">Why we need it!</h2>
<ul>
<li>Symfony Security is hard to learn π
<li>It enables a WOW effect for new developers π
<li>Still a great piece of software if you stay in the lines π
</ul>
</section>
<section>
<h2 class="no-caps">Why we need it!</h2>
<ul>
<li>This is the most used third party bundle π
<li>It's the entry point of a lot of new users, <br />
the user base that does not know Symfony very well πΆ
</ul>
<h4 class="no-caps">Maybe should help do better for the sake of Symfony? FOSUserBundle should be helpful, not scary.</h4>
</section>
<section>
<h2 class="no-caps">Hardly maintained π°</h2>
<p><strong class="emphasis">Issue overflow</strong>: everyone asks questions about the Symfony Security here,
thinking Security is FOSUser concern:</p>
<a href="https://github.com/FriendsOfSymfony/FOSUserBundle/issues/2290"><img style="max-width: 60%" src="images/2290.png" alt="Issue 2290"></a>
</section>
<section>
<h2 class="no-caps">Hardly maintained π°</h2>
<ul>
<li>Plenty of other examples, just looking at the first page:
<ul>
<li><a href="https://github.com/FriendsOfSymfony/FOSUserBundle/issues/2251">#2251</a> is resolved but the user does not close it</li>
<li><a href="https://github.com/FriendsOfSymfony/FOSUserBundle/issues/2223">#2223</a> is out of topic</li>
<li><a href="https://github.com/FriendsOfSymfony/FOSUserBundle/issues/2206">#2206</a> is user pushing stress on contributors to release a new version</li>
<li><a href="https://github.com/FriendsOfSymfony/FOSUserBundle/issues/2215">#2215</a> is question about email going to spam...</li>
</ul>
</li>
</ul>
</section>
<section>
<h2 class="no-caps">Hardly maintained π°</h2>
<ul>
<li>No release for more than a year (until this month)
<li>Slowed down by it's own popularity π
<li>Also, no strong labels management, no triage like FOSRest or FOSHttpCache π</li>
</ul>
</section>
<section>
<h2 class="no-caps">π Hack Day π</h2>
<ul>
<li>What are you doing <strong class="emphasis">this Saturday</strong>?
<li>Let's try to help the most used Bundle. Let's try to help newcomers.
<li>That's some serious "DX" (Developer eXperience) task!
<li>I want to help!
</ul>
</section>
<section>
<h2 class="no-caps">Building your own πͺ</h2>
</section>
<section>
<h2 class="no-caps">Building your own</h2>
<ul>
<li>Your own entities, no fuss, no extra fields
<li>Your own mailer from the start
<li>100% flexibility, 100% integrated to your code base
<li>Some code to write:
<ul>
<li>Your forms for register / profile and password reset</li>
<li>The appropriate controllers</li>
<li>The User Manager itself to create / persist, send emails, etc.</li>
</ul>
</li>
</ul>
</section>
<section>
<h2 class="no-caps">The User Entity</h2>
<h3>There is a <a href="http://symfony.com/doc/current/security/entity_provider.html">cookbook</a> for that</h3>
<ul>
<li>Create your User entity, implement UserInterface
<li>Configure Security to load from your Entity, <br >that's part of Symfony
</ul>
</section>
<section>
<h2 class="no-caps">The Registration form</h2>
<h3>There is a <a href="http://symfony.com/doc/current/doctrine/registration_form.html">cookbook</a> for that</h3>
<ul>
<li>Create a Form for the Entity
<li>Handle the Form Submission in a custom controller, where you have to encode the password
<li>Write a template
</ul>
</section>
<section>
<h2 class="no-caps">Building your own</h2>
<p>That's basic Symfony development. Same for password reset, profile edit...</p>
<p class="fragment">Just some decisions to make based on your needs and environment π π π<br />
Like, do you need <strong class="emphasis">canonical fields</strong>?</p>
</section>
<section>
<h2 class="no-caps">Canonical fields</h2>
<ul>
<li>FOSUserBundle adds canonical versions of all the username and email fields
<li><code>mb_convert_case($string, MB_CASE_LOWER);</code>
<li>This makes sure we can't have two accounts with the same email:<br>
</ul>
<p><code>foobar@example.org</code><br><code>FoOBAR@example.org</code></p>
</section>
<section>
<h2 class="no-caps">Canonical fields</h2>
<ul>
<li>Do you know what an <strong class="emphasis">SQL collation</strong> is for?
<li><pre><code class="hljs" data-trim>β¦ COLLATE utf8mb4_unicode_ci ENGINE = InnoDB;</code></pre></li>
<li>It tells how to <strong class="emphasis">sort the data</strong> in your table, to make sure "A" and "a" are before "Z" and "z"... which may not be the case in binary sort order</li>
</ul>
</section>
<section>
<h2 class="no-caps">With a proper collation</h2>
<h1><code>Γ’</code> = <code>Γ</code> = <code>A</code> = <code class="no-caps">a</code></h1>
<h2>π€</h2>
</section>
<section>
<h2 class="no-caps">Canonical fields</h2>
<h3 class="no-caps">It works for SELECT:</h3>
<pre><code class="hljs" data-trim>SELECT 'fΓΆoBAR@example.org' COLLATE UTF8_GENERAL_CI
= 'foobar@example.org' COLLATE UTF8_GENERAL_CI;
=> 1
</code></pre>
</section>
<section>
<h2 class="no-caps">Canonical fields</h2>
<h3 class="no-caps">It also works with UNIQUE KEY:</h3>
<pre><code class="hljs sql" data-trim>
CREATE TABLE `test` (
`username` varchar(180) COLLATE utf8mb4_unicode_ci,
UNIQUE KEY `uniqueindextest` (`username`)
) ENGINE=InnoDB DEFAULT
CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
INSERT INTO `test` (username) VALUES
('FOOBAR@example.org'), ('foobΓ€r@example.org');
=> Duplicate entry 'foobΓ€r@example.org'
=> for key 'uniqueindextest'
</code></pre>
</section>
<section>
<h2 class="no-caps">You do not need Canonical fields</h2>
<h1>π</h1>
</section>
<section>
<h2 class="no-caps">Choosing a bundle</h2>
<h3>The right way Β©</h3>
</section>
<section>
<h2 class="no-caps">Where to look</h2>
<ul>
<li>http://symfohub.com/ is dead π</li>
<li><a href="http://knpbundles.com/">KNPBundles.com</a> is ok but not up to date π</li>
<li><a href="https://packagist.org/">Packagist.org</a> is the best source! π
<ul>
<li class="fragment">Add <code>&type=symfony-bundle</code> to filter only the Symfony Bundle!</li>
</ul>
</li>
</ul>
</section>
<section>
<img src="images/packagist-before.png" alt="Before">
</section>
<section>
<img src="images/packagist-after.png" alt="After">
</section>
<section>
<h3 class="no-caps">Do not use Composer to install<br> π
jQuery π
</h3>
<h2 class="no-caps">Please</h2>
</section>
<section>
<a href="https://packagist.org/packages/jolicode/gif-exception-bundle">
<img src="images/packagist-full.png" alt="" style="width: 80%">
</a>
</section>
<section>
<a href="https://packagist.org/packages/jolicode/gif-exception-bundle">
<img src="images/packagist-full-ano.png" alt="" style="width: 80%">
</a>
</section>
<section>
<h2 class="no-caps">What to check</h2>
<ul>
<li>Is it maintained? Can I contribute? Bus factor?
<li>Is there any tests? Are they green?
<li>Is there a recent stable version?
<li>Is there a reasonable amount of issues?
<li>What are the dependencies? What are the dependencies of the dependencies?!
</ul>
</section>
<section>
<h2 class="no-caps">Almost 8200 bundles to choose from</h2>
<ul>
<li>Never install a bundle you do not trust 100%</li>
<li>What does it do and how easily can it be changed?
<li>Is there a complete documentation?
<li>Look at the issue tracker for long pending issues
<li>Does it add a real feature to Symfony, or is it just a library?
</ul>
</section>
<section>
<h2 class="no-caps">Wrapper Bundles</h2>
<ul>
<li>Wrapper around a perfectly fine PHP library
<li>The library moves faster than the bundle, and you have to update things manually
<li>In some cases the Symfony Bundle adds constraints on top of the Library, like FOSElasticaBundle:
<ul>
<li>Adds strict Configuration for the Elasticsearch mapping
<li>Elasticsearch mapping move faster than the bundle
<li>This has nothing to do with Elastica BTW
</ul>
</li>
</ul>
</section>
<section>
<h2 class="no-caps">Implementation Bundles</h2>
<ul>
<li>FOSUserBundle is an User Management implementation</li>
<li>You can use it if it fits your needs well</li>
<li>Otherwise you add a burden on your project, in term of maintenance and quality</li>
<li>You do not want a 5000+ lines of code Bundle to only use some parts of it</li>
</ul>
</section>
<section>
<h2 class="no-caps">3rd party Bundles</h2>
<ul>
<li>Keep your number of Bundle as low as possible β¬
<li>Prefer libraries over Bundles π π
<li>Stay awesome π
</ul>
</section>
<section>
<h2 class="no-caps">π― Wrap up π―</h2>
<ul>
<li>FOSUserBundle is a great tool, but it's an opinionated implementation, and should not be used on professional applications:
<ul style="font-size: 0.8em">
<li>Too much code to write on top of it for customization
<li>Makes maintenance and updates harder
</ul>
<li class="emphasis">We can help, join on Saturday π
</ul>
</section>
<section>
<h2 class="no-caps">π― Wrap up π―</h2>
<ul>
<li>Building your own User Management system is easy
<li>Third party bundles are good for quick win, but think about the long term consequences
<li>Each Bundle you install is long term engagement π§
</ul>
</section>
<section data-background="images/contribs.png">
<h2 class="no-caps">Thanks to all FOSUserBundle contributors</h2>
</section>
<section>
<h2 class="no-caps">I'm done β</h2>
<h4>Throw your questions at me!</h4>
<p>β€ <small>Did I told you I love emoji?</small> π¦</p>
<p>
<a href="https://twitter.com/damienalexandre">
<img src="images/supergeek.png" alt="Me"
style="width: 20%; vertical-align: middle; background-color: white!important; padding:10px;border-radius: 15px">
</a>
<br>@damienalexandre
</p>
</section>
<section>
<h2 class="no-caps">Personnal Wishlist!</h2>
<ul>
<li>Add strong label management for issues</li>
<li>Remove the Groups</li>
<li>Remove the AdvancedUserInterface, but provide example of how to add it</li>
<li>Remove the username field, but provide example of how to use it</li>
<li>Remove the last_login field, or provide a way to disable the listener</li>
<li>https://github.com/FriendsOfSymfony/FOSUserBundle/issues/1309</li>
</ul>
</section>
</div>
</div>
<footer class="joli">
Β« Do not (always) use FOSUserBundle Β» ‐ SymfonyCon Berlin 2016 ‐ <img src="lib/font/logo-fond-noir.svg"
style="height:1em; vertical-align: text-bottom;"/>
2016
</footer>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script src="js/emojione.js"></script>
<script>
var preload = new Image();
preload.src = "images/contribs.png";
// More info https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
transition: 'none', // none/fade/slide/convex/concave/zoom
// More info https://github.com/hakimel/reveal.js#dependencies
dependencies: [
{
src: 'lib/js/classList.js', condition: function () {
return !document.body.classList;
}
},
{
src: 'plugin/markdown/marked.js', condition: function () {
return !!document.querySelector('[data-markdown]');
}
},
{
src: 'plugin/markdown/markdown.js', condition: function () {
return !!document.querySelector('[data-markdown]');
}
},
{
src: 'plugin/highlight/highlight.js', async: true, callback: function () {
hljs.initHighlightingOnLoad();
}
},
{src: 'plugin/zoom-js/zoom.js', async: true},
{src: 'plugin/notes/notes.js', async: true}
]
});
// Emoji One
emojione.imageType = 'svg';
emojione.sprites = true;
emojione.imagePathSVGSprites = 'lib/emojione.sprites.svg';
delete emojione.jsEscapeMap["Β©"]; // Do not translate Β©
Reveal.addEventListener('ready', function (event) {
var emoji_nodes = document.querySelectorAll('section p, section li, section h1, section h2, section h3, section h4, section h5, section h6, footer');
for (var i = 0, len = emoji_nodes.length; i < len; i++) {
var element = emoji_nodes[i];
var input = element.innerHTML;
element.innerHTML = emojione.unicodeToImage(input);