Ben Davies

I would just point that that phpstorm, phpstan and psalm all support this syntax.

> `` is valid: > > > If the attribute is present, its value must either be the empty string or **a value that is an [ASCII case-insensitive](https://infra.spec.whatwg.org/#ascii-case-insensitive) match for...

still broken due to `composer dump-autoload --classmap-authoritative` worked around by putting this in my test cases: ```php if(!class_exists('ApiPlatform\Core\Bridge\Symfony\Bundle\Test\Constraint\ArraySubset', false)){ class_alias('ApiPlatform\Core\Bridge\Symfony\Bundle\Test\Constraint\ArraySubsetV9', 'ApiPlatform\Core\Bridge\Symfony\Bundle\Test\Constraint\ArraySubset'); } ```

this seems a step too far at the moment. for the moment, why can we not just make `PUT` mean `PUT` semantically, rather than `PATCH`? is is difficult? EDIT: from...

you are all using different database vendors so your issues are not going to be the same thing. I think @dvc issue may have been fixed by my PR: https://github.com/doctrine/dbal/pull/3158...

just to repeat the usual usecase for this type or thing, so the discussion is not lost: often libraries will have optional "suggested" dependencies, which, if installed by the consumer,...

FYI, I briefly experimented with: copying a composer.phar into the checked out project and running the phar, instead of running the composer installer php class directly. this seemed far faster...

Ah yes, gc. Do you mean you want to control the composer version? You could bundle a phar?

I'm not sure what you mean :) I was suggesting including a controlled composer phar in this project and using it to install project deps :)

@dhadka this may be relevant to you? can anything be done in the backend here?