PHPCS and PHPCBF are two well-know PHP scripts used in the PHP development to (PHPCS) detect violations of a defined coding standard, and (PHPCBF) to automatically correct coding standard violations.
I usually use both with composer in my WordPress projects, adding them as dependency in the composer.json file.
But sometimes I need to check some individual PHP file without adding PHPCS and PHPCBF as dependency. In this post, I am going to explain how I do this.
Sometimes, it is useful to use the WordPress nightly version on your local environment, to avoid problems with your code in the near future.
Sometimes you need to test some code, API functions,… in a WordPress plugin or theme without using anything else.
To do this, you can use the WP-CLI. Make sure you have installed it.
GlotPress has some PHPUnit tests. In this post, I will go to explain how to run it in your local machine.
I think it is a good practice to sign your Git commits. In this post, the author explains why and how to sign your Git commits. An interesting reading.
dump() and dd() are two useful debug helpers available in the Laravel framework.
In a talk at the WordCamp Spain online 2021 Adriá Cobo asked me one interesting question about these 2 functions (e() and esc_html_()):
If everything that is printed must be escaped, what is the point of _e()? Is it a legacy code?
In this post, I try to answer this question.
The current GlotPress API documentation (October 2021) was generated by ApiGen. Last commit was made on April 4th, 2016.
The last ApiGen commit was made on 23 Apr 2018, so I think this tool is deprecated. Furthermore, I was not able to use it with PHP 7.4 and GlotPress, so I look for another tool. The most PHP used tool is phpDocumentor. In this post I explain how to use it with GlotPress.
Install phpDocumentor globally on the machine, using the .phar tool.
Get the last .phar URL.
To run phpDocumentor, execute:
php phpDocumentor.phar run \
-d ~/code/wordpress/glotpress-env/glotpress.git \
-t ~/code/wordpress/glotpress-env/gp-docs \
~/code/wordpress/glotpress-env/glotpress.git is the GlotPress folder.
~/code/wordpress/glotpress-env/gp-docs is the documentation folder.
vendor/ is the folder where Composer stores all the information. It is located in the root folder of the project.
I have had some problems installing wordpress-develop on the M1 chip, so I describe here how I have solved it.
Laravel Valet is a development environment for macOS minimalists. It was developed to use in Laravel projects, but in this post, I will explain how to install and use with WordPress.