/explore
|
You are here 
|
andreas.heigl.org | ||
| | | | |
tomasvotruba.com
|
|
| | | | | One technology evolution sparks naturally another one. When electricity became accessible to masses, a huge industry of home-electric tools became possible. Like this tool, I currently write on. The same thing happens in software, just exponentially faster. Like tokens and AST sparked [tools that change your code](/blog/2018/10/22/brief-history-of-tools-watching-and-changing-your-php-code/). Recently, I introduced [Symfony Static Dumper](/blog/2020/03/16/statie-is-dead-long-live-symfony-static-dumper/) that uses YAML to store data in your Symfony application. You where this goes... how can **we turn this YAML into objects**? | |
| | | | |
apisyouwonthate.com
|
|
| | | | | We've been talking a lot about documentation and API descriptions recently. About how it's important to write down your contract using API descriptions, and how to turn these descriptions into beautiful human-readable documentation. Now let's look at how we can ensure that documentation is actually telling the truth! | |
| | | | |
dygalo.dev
|
|
| | | | | It is an article about using property-based testing in the scope of web applications. It covers the new tool named Schemathesis that generates test cases for applications based on Open API schemas. | |
| | | | |
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. | ||
