Fabio

@lmiller1990 I will give feedback this week if I still see this issue

@lmiller1990 so I updated and still seeing the error, now I cannot even use end to end testing. Node version 16.17.0 ```ts import { defineConfig } from 'cypress'; const getFromEnv...

@ZachJW34 So I had finally time to put something together where I am already seeing the issue: https://github.com/snake-py/minimal-bug-repo-cy-10 I added a Readme on how to use it. The repo has...

@amehta265 thank you for pointing out the workaround. This seems sufficient enough for me.

Well the issue I am facing is if I run prettier on my files and afterward I run [PHP_CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer) the changes prettier made will collide with the PSR-12 standard. This...

@czosel for instance: ```php foreach ($client->getContractsByCustomerId($customer["id"]) as $contract) { ``` prettier will do this: ```php foreach ( $client->getContractsByCustomerId($customer["id"]) as $contract ) { ``` I will now get the following error...

Hey, I opened a clarification ticket on the PSR12 guide about this and they told me that it is according to their standard "not okay" to break foreach up into...

@czosel I mean no offense, but this will make the plugin effectively useless to me, and probably other people as well. @cseufert > The PER-CS group suggest refactoring the loop...

Any further thoughts regarding this issue or do you just want to stick to the statement that this package is not written with the purpose to fulfill any coding standard?

> What’s the reason you feel that you have to be 100% PER-compliant Well, because our code quality check in our pipeline uses PSR-12 standards. The code quality check in...