Some time ago, I was integrating an external library into Magento 2. The library required API credentials to be passed into its constructor, so I thought environment variables (env vars) would be a perfect fit. Magento’s Dependency Injection (DI) system supports this—or so I thought. Well, it does in theory… or rather, I’ve used this method before.

I’d like to revisit the topic of using DTOs for handling forms in Symfony. It turns out there are a few points that could use some clarification. This time, the format will be a little different—I’ll focus on specific use cases and explain them.

A way to automate order processing in an ecommerce application. Long story short: delegate everything that can be problematic or waste someone else's time. In the end, your job is to sale things, not put them in boxes.

You’re building your first form in Symfony. What do you do? You check the documentation! But what if there’s a better way than the one described in the docs?

Most code examples that can be fount online tend to extend EntityRepository. But it's not the only way to work with Doctrine repositories. Here's one of the possible ways of define the repository differently.