Skip to content
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

Revert #1575 (Use a PHP-CS-Fixer shim rather than an external PHAR) #1654

Merged
merged 1 commit into from
Jan 15, 2025

Conversation

kbond
Copy link
Member

@kbond kbond commented Jan 15, 2025

This reverts #1575. This PR has caused a lot of trouble as it made php-cs-fixer a required dep which installs a recipe.

See #1644, #1653, #1651, #1648.

We can't have php-cs-fixer (or the shim) as a required dependency. I think we need to have this bundle only use php-cs-fixer if available/configured (or drop it entirely). I'm not sure why it is used at all - feels like a lot of added complexity...

@kbond kbond changed the title Revert "feature #1575 [make:*] Use a PHP-CS-Fixer shim rather than an external PHAR" Revert #1575 (Use a PHP-CS-Fixer shim rather than an external PHAR) Jan 15, 2025
@kbond kbond merged commit 468ff27 into symfony:main Jan 15, 2025
9 checks passed
@kbond kbond deleted the revert-1575 branch January 15, 2025 00:21
@alexander-schranz
Copy link

The why is mostly because php parser putput has no styling.
But I would like go the way rector does it by just document it that you should run your favorite code style fixer (phpcsfixer, ecs, ..) after you generated code. I would do nothing automaticall in my opinion.

@nicolas-grekas
Copy link
Member

I would do nothing automaticall in my opinion.

I agree with that: make-bundle should stick to one "Symfony CS" for output and any other CS is user's problem to solve.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants