-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
PHP 8.2 not supported #6764
Comments
I’m also surprised that PHP 8.2 is not yet supported, but I don’t think it’s a bug: there still are open issues on this topic. Last time I searched, |
This was the best category I could choose from the suggested ones in the "New issue" form. I know that there's no explicit declaration of supported versions, but since there's a stable There's also another blocker regarding the Anyway, fingers crossed for quick fixes on those bugs you mentioned 🤞 |
Folks, highly encouraging to use the search feature. |
@keradus is there any simple way to know which PHP version is currently supported by PHP CS Fixer? I don't see this info in the main README file, what do you think about adding this? I think it would help to avoid most (some) reported issues about unsupported PHP version |
it;s fair, @bocharsky-bw if you like to, could you suggest a PR adding this note? |
Let's move the discussion to PR then, thanks for picking up! |
@keradus have u a milestone, or sth like this about what tasks(goals) must be closed to support 8.2? |
This is what we identified so far, but not sure if all is identified already |
@keradus as all those issues are not closed, is there any reason not to mark PHP 8.2 as supported ? |
@stof what do you mean? PHP 8.2 is supported. Error described in the initial comment currently is visible for PHP 8.3. |
ah sorry, I missed the fact that the async-aws project was not using the latest version |
Bug report
Description
PHP CS Fixer is not working with PHP
8.2.*
Runtime version
Used command
Configuration file
Code snippet that reproduces the problem
n/a
The text was updated successfully, but these errors were encountered: