Skip to content

Fix compatibility with PHPCSFixer 2.x - #41

Open
lolautruche wants to merge 1 commit into
umpirsky:masterfrom
lolautruche:fix/phpCSFixer2
Open

Fix compatibility with PHPCSFixer 2.x#41
lolautruche wants to merge 1 commit into
umpirsky:masterfrom
lolautruche:fix/phpCSFixer2

Conversation

@lolautruche

Copy link
Copy Markdown
Contributor

Symfony upgrade fixer is currently locked with PHPCSFixer 1.10.* which is problem, especially if one has PHPCSFixer 2.x already installed globally with Composer.

This PR simply fixes it.
To make it work, I also removed support for PHP 5.4 in .travis.yml as it won't work with Symfony 3 (required by PHPCSFixer 2.x). And it's completely obsolete anyway now ;-).
I also removed hhvm since it's also abandoned.

Symfony upgrade fixer is currently locked with PHPCSFixer `1.10.*` which
is problem, especially if one has PHPCSFixer 2.x already installed
globally with Composer.

This PR simply fixes it.
To make it work, I also removed support for PHP 5.4 in `.travis.yml` as
it won't work with Symfony 3 (required by PHPCSFixer 2.x). And it's
completely obsolete anyway now ;-).
I also removed `hhvm` since it's also abandoned

@umpirsky umpirsky left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is nice, but the tests are failing.

I know PHP-CS-Fixer 2.0 is very different from 1.0, and not sure how complex it is to migrate. The tests are failing, and we should not only make tests green, but also test it with 2.0 on real codebase to make sure it does not break.

Thanks.

Comment thread .travis.yml
- 5.5
- 5.6
- 7.0
- 7.1

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add 7.2.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@lolautruche

Copy link
Copy Markdown
Contributor Author

Hi @umpirsky
Sure, I was unsure tests would pass since I didn't manage to run them (and now I understand why).
I can have a look to check the complexity.

In any case, this should go into a new major version (or v0.2) as this is a major change.

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.

2 participants