Giuseppe Mazzapica

Hi @henzeb thanks for your work. There's the discussion about to bring "link" functionality natively in Composer. The discussion started 8+ years ago in this issue and recently I'm trying...

@SanderSander If I understand correctly your plugin allows to link packages and link them (by creating a symlink) _after_ they are installed. So your plugin first let Composer pull the...

@naderman I've experienced that more often than not I need a "disposable" vendor folder. When something goes wrong I can often solve the issue by deleting the lock and the...

> You can select source install for specific packages But this means I have to change the `composer.json`, something I don't want to do in the project deployed online, meaning...

@naderman @Seldaek I spend some time in shaping an idea on how this could work. Where do I start a conversation? This is what I have so far: https://gist.github.com/gmazzap/b71e0d4eb99e0657d939bbc8d856bc7d Let...

@thefrosty we have a couple of lefotover instances of that string in v2, because PHP did not provide a replacement for it :(, and so we need to refactor https://github.com/inpsyde/Wonolog/blob/2.x/src/Data/Log.php...

@thefrosty The branch "2.x" is the alpha right now https://github.com/inpsyde/Wonolog/tree/2.x And it needs testing :) Docs: https://github.com/inpsyde/Wonolog/tree/2.x/docs are already updated

@thefrosty this is done for v2 https://github.com/inpsyde/Wonolog/blob/2.x/src/Registry/ProcessorsRegistry.php#L247 where we added return type. I don't think we want to support PHP 8.1 in v1.

Not have an ETA yet, but that is going to happen _soonish_. Actually, you can already try out the [`2.x` branch](https://github.com/inpsyde/Wonolog/tree/2.x) which is using Monolog 2.3.5+ and _should be_ fully...

Hi @benoitchantre the project is mainatined, and we have in use in _many_ production sites, os it is very unlikely it will die. The issue is that those many websites...