/explore
|
You are here 
|
phpstan.org | ||
| | | | |
tomasvotruba.com
|
|
| | | | | Upgrading Doctrine Fixtures can be challenging work. It requires the coordination of four different package groups on Github. One cannot be upgraded without the other. We first prepare for the jump, then take the leap with confidence. I'm writing this post as I handle the upgrade, so my thoughts are fresh, and the process is ongoing. It may evolve based on new information. Let's see where the rabbit hole goes. | |
| | | | |
tomasvotruba.com
|
|
| | | | | There are 2 ways to use PHPStan. You can use native levels, and official extensions and raise the level from 0 to 8. This is a good start, but it often requires enormous work and brings must-have value. There is also a 2nd way: I wanted PHPStan **to be more fun and more tailored to the unique projects I work with**. That's why I made [symplify/phpstan-rules](https://github.com/symplify/phpstan-rules), a package that just crossed 6 200 000 downloads. It is one of the most used PHPStan extensions apart from official ones. I put all the fun and practical rules there, and often they prove to be useful to others too. But today I want you to move from end-user to **creator**. | |
| | | | |
tomasvotruba.com
|
|
| | | | | In the previous post, we looked [at *how* to compile TWIG to raw PHP](/blog/stamp-1-how-to-compile-twig-to-php). It's one step forward, but it's not enough. Today we look at *how* we turn **the raw PHP code to the code PHPStan understands**. | |
| | | | |
www.github.com
|
|
| | | my blog, with astro. Contribute to Krayorn/blog development by creating an account on GitHub. | ||
