Thanks everyone a lot for your feedback. I would work harder in next time and sorry about that fiasco.
excellent talk
Cool to see what solutions were picked by opensky. We faced similar challenges and it nice to compare. Though it hit a nice balance between technical stuff and giving an overview.
Bit different from the rest of the talks. Was an open discussion where everyone was free to participate. Topic was really interesting and would have been better if it was 10 or 20 min longer.
We need more of these "soft" talks.
> If you have 2 services implementing same interface, why do you suggest to wire them thru the interface but not directly? This way you don't need to put an alias
but your code should not target wiring! your code should target SOLID principles! which means following the LSP principle, so coding against abstractions.
> Is it possible to use wildcard path specs in the config files (i.e. ../src/*/Controller)?
Yes, the entry is a glob pattern
> What is the overhead of using autowire vs getting services from container? Because it must involve Reflection...
None, Symfony's container is compiled
> Do the defaults apply to imported files as well?
no, defaults apply only to the current file
> Who want some beer tonight?
sure ;)
> What is the difference between service locator and container?
using Symfony v4 specific definitions to answer thuis question: a container is The container, ie the object that holds all services.
A service locator is a container that knows only about a short list of predeclared services (could be with a different id)
> Is it possible to extend the config of individual services with Annotations? Like setting one explicitly to public and/or add an alias
Using annotations to define DI config is not possible (it has been rejected several times as ppl/core-team were not convinced by it, but that's never a definitive answer ;-) )
> How to register a service from vendor/ to di?
using regular DI configuration. But if a vendor needs a DI config, then make that config a Flex recipe so that the vendor package is made easy to install
> Do we have to write down service spec when creating factory pattern classes or DI v4 will automatically do the work for us?
yes, factories cannot be automated. But if you think of Doctrine repositories, v1.8 of the DoctrineBundle provides a new base class repository that works with autowiring.
> Can I use patterns or wildcards in the resources param in services yml?
yes you can! (and it's recursive when defining services)
> How are tagged services injected into class? Array in constructor?
as iterator objects (RewindableGenerator class in DI component, but your should always use the "iterable" type hint, never this class directly)
> We have an additional sf event dispatcher in sulu when using autoconfig would the subscribers be called in both dispatcher. how could this be fixed?
advanced and new question, needs custom response, I don't what to give bad answer yet, community discussion needed
> When extending AbstractController is it really necessary implementing ServiceSubscriberInterface? Actually AbstractController already implements it
Correct, that was for the demo :)
This had almost nothing to do with Symfony so the title was misleading to say the least.
Other than that it was also a very general superficial talk and the speaker didn’t come of very enthousiastic.
Very good and entertaining talk. Of course the speaker being a native English speaker helps.
Maybe one or two real examples of how a native (non-Encore) webpack config file looks like could’ve helped showing the audience how great Encore is.
Webpack Encore seems like an indispensable tool already! Kutgw.
Good info, presented very well but a bit too general and low key for my taste; especially since it was marked as an “advanced” talk.
I’d assume any advanced/intermediate php/symfony developer knows unsetting a var clears up memory. Also batch operations are in the doctrine manual.
I hoped to learn new advanced techniques or insights; but that didn’t happen.
It was a good talk nonetheless; just not what I expected.
Nice summary of the entire week!
A lot of “oh that’s right” moment; so really helpful.
Very well presented too; good tempo and nice GIFs :-D
A nice summary of the changes in symfony over the last year. Slides were fun and had a light tone. Only point of criticism might be the accent and the obvious difficulties with speaking English. But practice makes perfect so don't let that stop you#