/explore
|
You are here 
|
mikemadison.net | ||
| | | | |
blog.martinhujer.cz
|
|
| | | | | ||
| | | | |
tomasvotruba.com
[Composer 2 was released](https://twitter.com/packagist/status/1319945203797708800) this week. It brings **massive `composer install/update` performance** improvement of [150-200 %](https://blog.packagist.com/composer-2-0-is-now-available). That means [faster feedback](/blog/2020/01/13/why-is-first-instant-feedback-crucial-to-developers/) from CI and faster monorepo testing. Today, we'll look on how to use Composer in Github Actions with monorepo split testing and what to avoid. |
|
| | | | | ||
| | | | |
daniel-siepmann.de
The composer package "maglnet/composer-require-checker" allows you to check whether all used dependencies are actually registered via composer. |
|
| | | | | ||
| | | | |
dogweather.dev
Does everyone already know about this? Am I just late to the party? I randomly discovered this, and it's blowing me away. Background: why match & exhaustiveness checking is cool First, here's a great run-down on Python 3.10's match statement. But Rust's "matches are exhaustive". I've always thought this is amazing, almost magical: Rust knows... |
|
| | | |||
