Changes

In the PHP community, as well as every other development community, there has been a long-standing tradition of establishing 'Coding Standards' that specify how developers should format their code. So, the [http://www.php-fig.org/ PHP Framework Interop(ability) Group] came up with <abbr title="PHP Standard Recommendation">[http://www.php-fig.org/psr/psr-1/ PSR-1]</abbr> and <abbr title="PHP Standard Recommendation">[http://www.php-fig.org/psr/psr-2/ PSR-2]</abbr> that deal with the issue specifically.

== Tools ==

*[https://cs.symfony.com/ PHP Coding Standards Fixer website] ([https://github.com/PHP-CS-Fixer/PHP-CS-Fixer code])*Note that if you use [[NetBeans]], there is a plugin that will integrate with this tool. Greg Sherwood (Squiz Labs) is the maintainer of '''[httphttps://wwwgithub.com/squizlabs.com/php-codesniffer PHP_CodeSniffer PHP CodeSniffer]''', which was originally a PEAR project. PHP_CodeSniffer is a PHP5 script that tokenises tokenizes and "sniffs" PHP, JavaScript and CSS files to detect violations of a defined coding standard. It is an essential development tool that ensures your code remains clean and consistent. It can also help prevent some common semantic errors made by developers. * [https://github.com/squizlabs/PHP_CodeSniffer/wiki/Usage Usage]* There is a [https://packagist.org/packages/mediawiki/mediawiki-codesniffer sniff file for MediaWiki] (see [https://github.com/wikimedia/mediawiki-tools-codesniffer here]) that you can use to conform to [[mw:Manual:Coding_conventions|MediaWiki Coding Conventions]] === ESLint ===[https://eslint.org/ ESLint] statically analyzes your code to quickly find problems. It is built into most text editors and you can run ESLint as part of your [[continuous integration]] pipeline. ESLint is used as a code quality tool for the MediaWiki project, and specifically their [[Vue.js|Vue]] codebase. More at https://www.mediawiki.org/wiki/Manual:Coding_conventions/Vue