-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension stopped working with complex JSON rules #217
Comments
Still having issues, v0.3.13 works fine. |
your os is linux, i can't test on linux. |
Works fine after update for me, thanks |
Parsing JSON works fine, but there are new problems. runAsync: spawn In ConfigurationResolver.php line 395: The path "break..."},"no_trailing_comma_in_list_call":true,"no_trailing_com fix [--path-mode PATH-MODE] [--allow-risky ALLOW-RISKY] [--config CONFIG] [--dry-run] [--rules RULES] [--using-cache USING-CACHE] [--cache-file CACHE-FILE] [--diff] [--format FORMAT] [--stop-on-violation] [--show-progress SHOW-PROGRESS] [--sequential] [--] [...] |
new version published, test again |
Works fine after update, thanks |
Recently extension stopped working properly.
When I'm using complex rules settings like:
I receive an error:
When I'm using simple rules like
"php-cs-fixer.rules": "@PSR12",
everything works ok:The text was updated successfully, but these errors were encountered: