Open glensc opened 5 years ago
is_null
in place
- not directly. i was about to make changes, but noticed
is_null
in place
I see.
- i don't use the tool. shouldn't travis complain on this?
It's not doing that currently. It makes sense to do only, when we fix all existing issues to avoid all new build be broken by default.
checked vendor/bin/phpcs
, the changes here are not related.
Maybe can combine all CS fixes into single PR? I've just updated composer.json
and composer.lock
to ensure that used CS is compatible with latest PHP_CodeSniffer version.
PHP_CodeSniffer also does support auto-fixing of most, but not all issues found.
If you're using PhpStorm, then you configure it to automatically highlight problematic places.
We're not using Scrutinizer CI or otherwise it will be showing CS issues online as well.
You can squash merge from GitHub web UI if you have enabled that in project. If that's what you mean by single commit.
At this moment, I do not plan to make more CS fixes.
Minor code style fixes done with help of php-cs-fixer.