Philip Ardery

Results 206 comments of Philip Ardery

@ondrejmirtes I've updated the `phpstan` output obfuscation to be more clear and broken it into chunks with the corresponding code below each chunk. I've also marked the phpstan errors lines...

for some reason, upgrading `doctrine/orm` from `2.19.0` to `3.1.0` caused this error to go away... despite causing [errors elsewhere](https://github.com/phpstan/phpstan-doctrine/issues/551) with doctrine.

I had to roll back that `orm` change, but these errors mysteriously disappeared again. I was ignorning the errors yesterday. In an unrelated task, I deleted and reinstalled my vendor...

Agreed, this would be slick, especially given compelling reasons for using php configs over yaml, which is suspect will become the new norm https://getrector.com/blog/modernize-symfony-configs

hey @ondrejmirtes, just wanted to check in on this or perhaps the answer is, it simply isn't supported at this time (due to https://github.com/phpstan/phpstan-doctrine/issues/529)?

extremely helpful, I really appreciate you taking the time to provide such a helpful response!

@ondrejmirtes I've just tested and getting the same results on orm `3.2.1` using `->serverVersion('8.0.25')` in my doctrine config. Is there something I should debug/dump that would be helpful? EDIT: this...

@ondrejmirtes I think the `serverVersion` issue demonstrated [here](https://github.com/phpstan/phpstan-doctrine/issues/551#issuecomment-1979286320), which you [explained](https://github.com/phpstan/phpstan-doctrine/issues/551#issuecomment-2196434344) how to fix, was a red herring. This issue was suddenly triggered on dbal `4` because a new deprecation...

@XjSv doesn't drupal copy the files from vendor? if so, and this isn'tworking, the patching must be executed after drupalcopies the files from composer. Sounds like it might be the...