I’m a big fan of xdebug I’ve been using it for years to dig into scripts.
But I’ve only used it on websites. And as I’m dipping my toes into wp-cli the need for command line debugging is increasing.
Like often Jetbrains has a good guide to set it up: “Working with Remote PHP Interpreters in PhpStorm”
For those interested in xdebug and PhpStorm start here.
for ( $i=0; $i <= 5; $i++ ) {
echo "for $i <br/>\n";
}
echo "done $i <br/>\n";
What will $i be, when the loop is done?
It will be 6 not 5.
Can be usefull if you need to skip the last item in a (numbered) array
During WordCamp Rotterdam I worked on a small bug in WP-CLI. A bug I found roughly six months ago.
The bug itself was a one line fix.
I was asked to create functional tests using behat which I didn’t even heard off.
So after checking the handbook and with help of a few others. It resulted in this pull request.
And now we wait.
Consider this dummy snippet:
if ( true === $skip || heavy_check() ){
continue;
}
The $skip is checked first. It is very quick as it is just a simple variable check. and since this is an ‘or’ statement. As soon as $skip is true it won’t bother with the heavy_check.
Something I always suspected but today I tested this and confirmed it.