Skip to content

CS: Add PHP 5.3 compatibility#39

Merged
Potherca merged 2 commits intoPHPCSStandards:masterfrom
GaryJones:5.3-compatibility
Sep 18, 2017
Merged

CS: Add PHP 5.3 compatibility#39
Potherca merged 2 commits intoPHPCSStandards:masterfrom
GaryJones:5.3-compatibility

Conversation

@GaryJones
Copy link
Copy Markdown
Contributor

Logically follows on from #38, though isn't strictly dependent on it being merged.

The use of short syntax for arrays was the only thing stopping this package from being compatible with PHP 5.3 as well. PHP 5.3 is specified in the Travis CI config. Allowing it to be used in setups that require PHP 5.3 makes it usable for more authors (such as those in the WordPress community).

Composer also requires PHP 5.3.2 to run, so it makes sense to ensure it works with that too.

The use of short syntax for arrays was the only thing stopping this package from being compatible with PHP 5.3 as well. This makes it usable for more authors (such as those in the WordPress community).
@Potherca
Copy link
Copy Markdown
Member

Potherca commented Sep 8, 2017

Since this package does not use any explicit PHP 7.0 or 7.1 features, I think it would be sensible to follow the version constraint set by Composer.

@GaryJones
Copy link
Copy Markdown
Contributor Author

GaryJones commented Sep 15, 2017

@frenck Any feedback on this?

Here's an example of a failing Travis build which is now stopping PRs from being merged.

screen shot 2017-09-15 at 13 09 12

@Potherca Potherca added this to the v0.4.3 milestone Sep 18, 2017
@Potherca
Copy link
Copy Markdown
Member

Potherca commented Sep 18, 2017

Unlike the VersionEye check that failed in PR-38, this check fails because of License whitelist issues.

screenshot from 2017-09-18 09-40-37

I've added the PHP license to the whitelist. I've Triggered the check again by finding the payload in the Webhooks Settings and pressing the ↻ Redeliver button.

@Potherca Potherca merged commit 63c0ec0 into PHPCSStandards:master Sep 18, 2017
@GaryJones GaryJones deleted the 5.3-compatibility branch September 18, 2017 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants