Docs: Fix constant/function assignment in WP example #1094
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also use camelCase for variables
tyrann0us
changed the title
|
Hi @theofidry, could I ask you to check this PR? Thank you! 🙏🏽 |
|
Thank you @tyrann0us! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Docs update
What is the current behavior? (You can also link to an open issue here)
In the WordPress code example, lists of constants are assigned to
exclude-functions, and lists of functions are assigned toexclude-constants. Also, there are typos: "Wordpress".What is the new behavior (if this is a feature change)?
Correctly assign constants to
exclude-constantsand functions toexclude-functions. Change variable naming to camelCase as part of the Boy Scout rule.Also, fix typos to "WordPress".
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information:
The scope of the PR changed from fixing the typos to fixing the constants/functions list assignment.