-
Notifications
You must be signed in to change notification settings - Fork 5
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-cs-fixer version used is different (lower) compared to core #113
Comments
GitMate.io thinks a possibly related issue is #55 (php-cs-fixer). |
PR #114 bumps all the little things that are waiting. |
Thanks for raising - however - it is not critical. Generally speaking - we will move forward with having CLI tools like php-cs-fixer / phan / phpstan etc. in a seperate namespace ( via composer-bin-plugin ) so the dependencies of these tools are segregated. I would not go forward with providing any manual version bumps - dependabot should be used for this. If it is not working as intended, please raise a ticket and we need to schedule time to look into it |
The bot had found a few things. But that php-cs-fixer bump has been "out there on the internet" for some time (and has a fix for something I reported...). Somehow the bot had not noticed it - maybe the bot was not looking at the dependencies under |
The bot did find everything that is officially published: https://packagist.org/packages/owncloud/coding-standard As we locked php-cs-fixer with 1.0.1 of the Opened an issue here: owncloud/coding-standard#14 |
I think we can close this - the PR is merged. |
I have seen that the version of php-cs-fixer used is different compared to core.
I compared both composer.lock files.
Background
php-cs-fixer errors in PR #112 with:
According to
https://stackoverflow.com/questions/51667079/netbeans-php-cs-fixer-end-up-with-error-files-that-were-not-fixed-due-to-errors
this could be due to an error of the used version and is possibly fixed by an update
core
files_primary_s3
@phil-davis @DeepDiver1975
The text was updated successfully, but these errors were encountered: