/explore
|
You are here 
|
tomasvotruba.com | ||
| | | | |
matthiasnoback.nl
|
|
| | | | | Part I: Don't use the standard controller The general belief is that controllers are the most tightly coupled classes in every application. Most of the time based on the request data, they fetch and/or store persistent data from/in some place, then turn the data into HTML, which serves as the response to the client who initially made the request. So controllers are "all over the place", they glue parts of the application together which normally lie very far from each other. This would make them highly coupled: they depend on many different things, like the Doctrine entity manager, the Twig templating engine, the base controller from the FrameworkBundle, etc. | |
| | | | |
blog.bitexpert.de
|
|
| | | | | Learn how to encrypt sensitive user data in your Symfony & Doctrine application using the specshaper/encrypt-bundle bundle. Easily encrypt and decrypt data with Doctrine events, without adding operational complexity to your project. | |
| | | | |
www.beberlei.de
|
|
| | | | | ||
| | | | |
wpdev.gwg.us
|
|
| | | [AI summary] This is a development test site for the indie Nintendo Switch game Ticket to Ride Europe containing placeholder content. | ||
