Guilherme Saade

@VasasA I already reviewed it — your code needs to be refactored before it can be merged. Right now, lack of spare time is what’s preventing me from doing it....

@Bender-0 please follow these steps: First, update your fork by going to your fork's Github page and pressing "Sync Fork" From your terminal: `git checkout 4.x` `git pull` `git checkout...

Can you please resolve the conflicts if you still want this feature? Thanks

This PR fixes this behavior: https://github.com/open-southeners/vscode-laravel-pint/pull/79

@Johnrivera7 Please wait for the next review batch. In the meantime, take a moment to read our contribution guidelines, your plugin file currently doesn’t follow them at all.

I’m going to close this one. Please make sure to follow our guidelines for submitting new plugins. Your plugin file doesn’t meet the minimum required structure for review.

@tonymans33 You don’t need to ask for a review every day. Reviews are processed in batches, not daily.

Oh, this looks like an issue with the latest version of `laravel/pint` `1.25.0` i can confirm that in `1.24.0` this problem does not occur. Might be related to: https://github.com/laravel/pint/pull/390

> Experimented with waiting for the spawn process to exit. This caused the extension to hang until I explicitly closed stdin in the child process. --- > @saade, that means...

@d8vjork The `--repair` flag was introduced in `v1.15.3` we're now at `v1.25.1`. Pint `v1.15.3` requires Laravel `^10.48.8` which is now sunsetted according to the [Support Policy](https://laravel.com/docs/12.x/releases#support-policy) Seems like a good...