Based on the standard practices of every programmer, each organization has its own coding standards. <\/p>\n\n\n\n
<\/p>\n\n\n\n
PHP Coding Standards are important because there may be many programmers working on different modules.<\/p>\n\n\n\n
<\/p>\n\n\n\n
If each of them made their own coding standards, the source code would become very hard to manage, which would make it impossible to fix in the future.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Reason to maintain the coding standards:<\/strong><\/p>\n\n\n\n <\/p>\n\n\n\n The following are a few recommendations to follow in order to maintain the standard of PHP coding.<\/p>\n\n\n\n <\/p>\n\n\n\n To separate PHP code, you must use the standard PHP tags<\/strong> instead of the shorthand tags. <\/p>\n\n\n\n <\/p>\n\n\n\n This is required by PHP and is also the easiest way to include PHP code on different operating systems and in different ways.<\/p>\n\n\n\n <\/p>\n\n\n\n Standard PHP Tag:<\/strong><\/p>\n\n\n\n <\/p>\n\n\n\n Shorthand PHP Tag:<\/strong><\/p>\n\n\n\n <\/p>\n\n\n\n When appropriate, use single and double quotation marks. If you are not evaluating any of the string’s contents, use single quotes<\/strong>.<\/p>\n\n\n\n You should almost never need to escape quotes within a string, as you may just alternate your quoting style:<\/p>\n\n\n\n <\/p>\n\n\n\n Since <\/p>\n\n\n\n Only one space should exist between the path<\/strong> and the include\/require keywords.<\/p>\n\n\n\n <\/p>\n\n\n\n It is strongly advised that <\/p>\n\n\n\n If your application depends on the file being loaded, this will probably cause other <\/p>\n\n\n\n Therefore, <\/p>\n\n\n\n Use lowercase letters for naming variables, actions, and functions (never camelCase<\/strong>). Separate each word with underscores. <\/p>\n\n\n\n <\/p>\n\n\n\n Do not abbreviate variable names excessively; the code should be self-documenting and straightforward.<\/p>\n\n\n\n <\/p>\n\n\n\n Class, trait, interface, and enum names should use capitalized and underscore-separated terms. All acronyms should be capitalized.<\/p>\n\n\n\n <\/p>\n\n\n\n Constants should be capitalized with underscores between each word.<\/p>\n\n\n\n <\/p>\n\n\n\n The names of files should be descriptive and all lowercase<\/strong>. Words should be separated by hyphens<\/strong>.<\/p>\n\n\n\n <\/p>\n\n\n\n After commas and between logical, arithmetic, comparison, string, and assignment operators, always use spaces.<\/p>\n\n\n\n <\/p>\n\n\n\n Put spaces around the control structure parenthesis.<\/p>\n\n\n\n <\/p>\n\n\n\n Defining a function:<\/strong><\/p>\n\n\n\n <\/p>\n\n\n\n Calling a function:<\/strong><\/p>\n\n\n\n <\/p>\n\n\n\n Performing Logical Comparisons:<\/strong><\/p>\n\n\n\n <\/p>\n\n\n\n Always use the abbreviated form of Typecasts, (int) rather than (integer) and (bool) rather than (boolean), and write it with lowercase letters. <\/p>\n\n\n\n <\/p>\n\n\n\n However, for float casting, use (float), not (float) (real). This function is deprecated in PHP 7.4 and eliminated in PHP 8.<\/p>\n\n\n\n <\/p>\n\n\n\n In certain cases, while discussing array items, you should only place a space around the index if it is a variable, as seen below.<\/p>\n\n\n\n <\/p>\n\n\n\n In a switch block, however, there should be no spaces between the case condition and the colon.<\/p>\n\n\n\n <\/p>\n\n\n\n Likewise, return-type declarations should not have a space before the colon.<\/p>\n\n\n\n <\/p>\n\n\n\n Except as explicitly indicated, parentheses should contain spaces.<\/p>\n\n\n\n <\/p>\n\n\n\n When employing these operators, there should be no space between the increment (++) or decrement (–) operator and the variable it applies to.<\/p>\n\n\n\n <\/p>\n\n\n\n Your indentation should always match the structure of your argument. Use actual tabs, not spaces, as this provides for the best client compatibility.<\/p>\n\n\n\n <\/p>\n\n\n\n If you have a block of code that would be easier to read if it were aligned, use spaces instead of tabs.<\/p>\n\n\n\n <\/p>\n\n\n\n Associative arrays are the next topic covered in this section. When an array has many items, each item should begin on a new line.<\/p>\n\n\n\n <\/p>\n\n\n\n Note the comma after the final array item; this is suggested since it makes it simpler to adjust the array’s order and produces clearer differences when new items are added.<\/p>\n\n\n\n <\/p>\n\n\n\n For switch control structures, case statements must be indented one tab after the switch statement, and case contents must be indented one tab after the case condition statement. <\/p>\n\n\n\n <\/p>\n\n\n\n As a general rule, tabs should be used at the beginning of the line for indentation, while spaces can be used for alignment in the middle of the line.<\/p>\n\n\n\n <\/p>\n\n\n\n Remove trailing whitespace from each line’s conclusion. It is preferred to omit the closing PHP tag at the conclusion of a file. <\/p>\n\n\n\n <\/p>\n\n\n\n If you employ the tag, remove any trailing spaces. A function body should not have any trailing blank lines.<\/p>\n\n\n\n Using long array syntax ( <\/p>\n\n\n\n Additionally, it is considerably more descriptive for novices. Arrays must be declared using the long array syntax.<\/p>\n\n\n\n When a function call is divided across many lines, each parameter must be on a distinct line. Single-line inline comments may occupy a separate line.<\/p>\n\n\n\n <\/p>\n\n\n\n Each parameter must not exceed a single line in length. Parameter values that span many lines must be assigned to a variable and then given to the function call.<\/p>\n\n\n\n <\/p>\n\n\n\n Before and after type declarations must have precisely one space. <\/p>\n\n\n\n <\/p>\n\n\n\n There should be no space between the nullability operator (?) and the actual type, as it is considered part of the type declaration.<\/p>\n\n\n\n <\/p>\n\n\n\n Class\/interface\/enum name-based type declarations must match the case of the declared class\/interface\/enum name, whereas keyword-based type declarations must be in lowercase.<\/p>\n\n\n\n <\/p>\n\n\n\n There shouldn’t be a space between the closing brackets of a function declaration and the colon that starts a return-type declaration.<\/p>\n\n\n\n <\/p>\n\n\n\n These rules apply to all structures allowing for type declarations: functions, closures, enums, catch conditions, as well as the PHP 7.4 arrow functions and typed properties.<\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Code standards<\/strong> consist of principles, procedures, and guidelines for producing code that is cleaner, more legible, and more efficient with fewer defects and errors. <\/p>\n\n\n\n <\/p>\n\n\n\n In addition, they provide a standardized method for developers to construct highly functional programs.<\/p>\n\n\n\n <\/p>\n\n\n\n Remember that coding standards are not subjective viewpoints; rather, they are actual guidelines that determine the programming style, techniques, and methods of your code. <\/p>\n\n\n\n <\/p>\n\n\n\n They must be specified openly and made accessible to developers. Coding standards<\/strong> ensure that all programmers adhere to specific principles. <\/p>\n\n\n\n <\/p>\n\n\n\n Therefore, every developer, including novices, can easily comprehend, debug, and maintain the code. <\/p>\n\n\n\n <\/p>\n\n\n\n Your team’s source code should look as if it were written by a single developer in a single session. <\/p>\n\n\n\n <\/p>\n\n\n\n PHP Framework Interop Group has issued the PHP Standard Recommendation (PSR) as a PHP specification. <\/p>\n\n\n\n <\/p>\n\n\n\n Similar to the Java Specification Request for Java, this document serves to standardize PHP programming ideas. <\/p>\n\n\n\n <\/p>\n\n\n\n It accomplishes this by outlining a shared set of norms and expectations for formatting PHP code.<\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n In summary, we’ve examined the PHP coding standards and demonstrated how to write correct code with examples.<\/p>\n\n\n\n Lastly, if you want to learn more about PHP, please leave a comment below. We\u2019ll be happy to hear it!<\/p>\n","protected":false},"excerpt":{"rendered":" Based on the standard practices of every programmer, each organization has its own coding standards. PHP Coding Standards are important because there may be many programmers working on different modules. … <\/p>\n\n
\n
\n
\n
Opening and Closing PHP Tags<\/strong><\/h2>\n\n\n\n
<php\n \/\/php code here\n?><\/code><\/pre>\n\n\n\n<?\n \/\/php code here\n?><\/code><\/pre>\n\n\n\nSingle and Double Quotes<\/strong><\/h2>\n\n\n\n
<?php\n \/\/ this is an example using a single quotation marks\n echo '<a href=\"#\" class=\"button\">This is using Single Quotes<\/a>';\n echo '<br>';\n \/\/ this is an example using double quotation marks\n echo \"<a href='{$escaped_link}'>This is using Double Quotes<\/a>\";\n\n \/\/ the incorrect way\n echo \"<a href=\"#\" class=\"button\">This is using Single Quotes<\/a>\";\n echo '<a href='{$escaped_link}'>This is using Double Quotes<\/a>';\n?><\/code><\/pre>\n\n\n\nWriting include\/require statements<\/strong><\/h2>\n\n\n\n
include[_once]<\/mark><\/code> and require[_once]<\/mark><\/code> are language constructs, they do not require parentheses around the path; therefore, they should not be used. <\/p>\n\n\n\nrequire[_once]<\/mark><\/code> unconditional includes be used. When using include[_once]<\/mark><\/code>, PHP will throw a warning when the file is not found but will continue execution. <\/p>\n\n\n\nerrors<\/em><\/strong><\/mark><\/code>, warnings<\/em><\/mark><\/code><\/strong>, or notices<\/em><\/mark><\/code> <\/strong>to be thrown, which could leave security holes.<\/p>\n\n\n\nrequire[_once]<\/mark><\/code> is the preferred option, as it throws a Fatal Error<\/em><\/strong><\/mark><\/code> if the file cannot be located.<\/p>\n\n\n\n<?php\n \/\/ This is the correct way\n require_once 'header.php';\n\n \/\/ The Incorrect way of writing include and require statements\n include_once ( 'file-name.php' );\n require_once __DIR__ . '\/file-name.php';\n?><\/code><\/pre>\n\n\n\nNaming Conventions<\/strong><\/h2>\n\n\n\n
<?php\n \/\/ Do this\n function some_name( $some_variable ) {}\n\n \/\/ Don't do this\n function someName( $variableName ) {}\n?><\/code><\/pre>\n\n\n\n<?php\n class Walker_Category extends Walker {}\n class WP_HTTP {}\n\n interface Mailer_Interface {}\n trait Forbid_Dynamic_Properties {}\n enum Post_Status {}\n?><\/code><\/pre>\n\n\n\n<?php\n define( 'PI_VALUE', true );\n?><\/code><\/pre>\n\n\n\n<?php\n require 'my-plugin-name.php';\n?><\/code><\/pre>\n\n\n\nSpace Usage<\/strong><\/h2>\n\n\n\n
<?php\n SOME_CONST === 50;\n foo() && bar();\n ! $bar;\n array( 7, 3, 5 );\n $baz . '-5';\n $term .= 'X';\n if ( $object instanceof Post_Type_Interface ) {}\n $result = 3 ** 3; \/\/ 27\n?><\/code><\/pre>\n\n\n\n<?php\n foreach ( $foo as $bar ) {\n ...\n }\n?><\/code><\/pre>\n\n\n\n<?php\n function my_function( $param1 = 'sample', $param2 = 'text' ) { ...\n\n function my_other_function() { ...\n?><\/code><\/pre>\n\n\n\n<?php\n sample_function( $param1, func_param( $param2 ) );\n sample_function2();\n?><\/code><\/pre>\n\n\n\n<?php\n if ( ! $sample ) { ... }\n?><\/code><\/pre>\n\n\n\n<?php\n foreach ( (array) $sample as $sample2 ) {\n ...\n $sample = (bool) $sample2;\n?><\/code><\/pre>\n\n\n\n<?php\n $z = $x['y']; \/\/ Correct.\n $z = $x[ 'y' ]; \/\/ Incorrect.\n\n $z = $x[0]; \/\/ Correct.\n $z = $x[ 0 ]; \/\/ Incorrect.\n\n $z = $x[ $y ]; \/\/ Correct.\n $z = $x[$y]; \/\/ Incorrect.\n?><\/code><\/pre>\n\n\n\n<?php\n switch ( $x ) {\n case 'yyy': \/\/ Correct.\n case 'yy' : \/\/ Incorrect.\n}\n?><\/code><\/pre>\n\n\n\n<?php\n function sum( $x, $y ): int {\n return $x + $y;\n }\n?><\/code><\/pre>\n\n\n\n<?php\n if ( $a && ( $b || $c ) ) { ...\n\n sample_function( ( $x - 1 ) * 5, $y );\n?><\/code><\/pre>\n\n\n\n<?php\n \/\/ Correct.\n for ( $x = 0; $x < 10; $x++ ) {}\n\n \/\/ Incorrect.\n for ( $x = 0; $x < 10; $x ++ ) {}\n ++ $a; \/\/ Multiple spaces.\n?><\/code><\/pre>\n\n\n\nIndentation<\/strong><\/h2>\n\n\n\n
<?php\n[tab]$x = 'text value here';\n[tab]$x2 = 'text value here2';\n[tab]$x3 = 'text value here3';\n[tab]$x4 = 'text value here4';\n?><\/code><\/pre>\n\n\n\n<?php\n $query = new Query( array( 'ref_id' => 95876 ) );\n?><\/code><\/pre>\n\n\n\n<?php\n $args = array(\n [tab]'post_type' => 'page',\n [tab]'post_author' => 95876,\n [tab]'post_status' => 'publish',\n );\n \n $query = new Query( $args );\n?><\/code><\/pre>\n\n\n\n<?php\n $sample_array = array(\n [tab]'x' => 'text value here',\n [tab]'x2' => 'text value here 2',\n [tab]'x3' => 'text value here 3',\n [tab]'x4' => 'text value here 4',\n );\n?><\/code><\/pre>\n\n\n\n<?php\n switch ( $type ) {\n [tab]case 'var1':\n [tab][tab]some_function();\n [tab][tab]break;\n [tab]case 'var2':\n [tab][tab]some_function();\n [tab][tab]break;\n }\n?><\/code><\/pre>\n\n\n\nRemove Trailing Spaces<\/strong><\/h2>\n\n\n\n
Declaring Arrays<\/strong><\/h2>\n\n\n\n
array(1, 2, 3)<\/mark><\/code> ) to declare arrays is typically more understandable than using short array syntax ( [1, 2, 3]<\/mark><\/code> ), especially for persons with vision impairments. <\/p>\n\n\n\nMultiline Function Calls<\/strong><\/h2>\n\n\n\n
<?php\n $bar = array(\n 'use_this' => true,\n 'meta_key' => 'field_name',\n );\n $baz = sprintf(\n __( 'Hi, %s!', 'domain_text' ),\n $friend_name\n );\n\n $a = x(\n $x1,\n $x2,\n sprintf( __( 'My favorite food is %s.' ), 'pizza' )\n);\n?><\/code><\/pre>\n\n\n\nType declarations<\/strong><\/h2>\n\n\n\n
<?php\n \/\/ Correct.\n function foo( Class_Name $parameter, callable $callable, int $number_of_things = 0 ) {\n \/\/ Do something.\n }\n\n function bar(\n Interface_Name&Concrete_Class $param_a,\n string|int $param_b,\n callable $param_c = 'default_callable'\n ): User|false {\n \/\/ Do something.\n }\n \n \/\/ Incorrect.\n function baz(Class_Name $param_a, String$param_b, CALLABLE $param_c ) : ? iterable {\n \/\/ Do something.\n }\n?><\/code><\/pre>\n\n\n\nFrequently Ask Questions (FAQs)<\/strong><\/h2>\n\n\n\n
What are the coding standards in PHP?<\/strong><\/h3>\n\n\n\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
What are PHP coding standards?<\/strong><\/h3>\n\n\n\n
Is PHP standardized?<\/strong><\/h3>\n\n\n\n
Related Articles<\/strong><\/h2>\n\n\n\n
\n
Summary<\/strong><\/h2>\n\n\n\n