-
-
Notifications
You must be signed in to change notification settings - Fork 518
Add GlobalVariablesOverride standard doc #2586
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,32 @@ | ||||||
<?xml version="1.0"?> | ||||||
<documentation xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | ||||||
xsi:noNamespaceSchemaLocation="https://phpcsstandards.github.io/PHPCSDevTools/phpcsdocs.xsd" | ||||||
title="Global Variables Override" | ||||||
> | ||||||
<standard> | ||||||
<![CDATA[ | ||||||
WordPress global variables should not be overridden. | ||||||
|
||||||
Two WordPress global variables, `$content_width` and `$wp_cockneyreplace`, are | ||||||
specifically intended to be overridden by themes/plugins and are exempt from this rule. | ||||||
]]> | ||||||
</standard> | ||||||
<code_comparison> | ||||||
<code title="Valid: Different variable name."> | ||||||
<![CDATA[ | ||||||
<em>$my_query</em> = new WP_Query( $args ); | ||||||
|
||||||
|
||||||
<em>$GLOBALS['my_data']</em> = "some data"; | ||||||
]]> | ||||||
</code> | ||||||
<code title="Invalid: Global variable overridden."> | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
I think it is important to mention that this is about WordPress globals and not any globals. |
||||||
<![CDATA[ | ||||||
<em>global $wp_query;</em> | ||||||
<em>$wp_query</em> = new WP_Query( $args ); | ||||||
|
||||||
<em>$GLOBALS['wp_query']</em> = new WP_Query( $args ); | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Nitpick: maybe use a different global here to illustrate one more WP global that is flagged by this sniff? |
||||||
]]> | ||||||
</code> | ||||||
</code_comparison> | ||||||
</documentation> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about this title. Maybe
Valid: Using custom variable/key names instead of WordPress globals.
orValid: Using custom variable/key names.
is a bit better and more descriptive? Happy to hear other suggestions you might have.The concern that I have with
Valid: Different variable name.
is that it reads a bit vaguely and doesn't clearly communicate what makes the examples below valid.