One thing that's super useful for new users is code examples. Right now, the biggest problem for someone to start using PHP_CodeSniffer is lack of a list of available Sniffers with their options and examples. From what I know to get a list of all sniffs right now, you have to go through source code in src/Standards, and it's exhausting. Something like [mlocati/phpPHP-cs-fixer-configurator](htt

I don't think it is correct to generate code which will put an argument with a default value before an argument without a default value.

In the example the generated code produces a function like that:

function bar(int $a = null, string $b, bool $c, callable $d = null) : float

This means the first argument is optional, but the second and third aren't.

I realise = null i

Nice! Please add the following to README.md to make Laravel the default standard.
Link (or copy) Laravel into the global CodeSniffer directory.
Mac OSX Homebrew example:
ln -s LaravelCodeSniffer/Standards/Laravel/ /usr/local/etc/php-code-sniffer/Standards/
Set Laravel as default:
phpcs --config-set default_standard Laravel
Details at https://github.com/squizlabs/PHP_CodeSniffer/wiki/Conf

In https://github.com/WPTRT/WPThemeReview/blob/develop/WPThemeReview/Sniffs/PluginTerritory

https://github.com/stevegrunwell/wp-enforcer/blob/develop/bin/hooks/pre-commit#L9

This line is hard-coded and does not respect the -c flag of the CLI.

# Determine if we have a phpcs.xml file
if [[ -f ./phpcs.xml ]]; then
	standard="--standard=./phpcs.xml"
else
	standard=''
fi

The above needs to be updated to accept an arg when -c is set in the CLI.

1. More JavaScript teams do this (e.g. airbnb, standard, npm, node, google/angular, facebook/react, prettier).
2. It's easier to type (no shift needed on most keyboards).
3. Allows easier write html within javascript
4. Single quotes can often look better when you're using them to represent an empty string '' vs "" (too many little marks in the latter and can be difficult read)

Issue Overview

When requesting a report for a specific version of a plugin, if Tide doesn't yet have a report for it it'll start to generate one and return a <p>pending</p> response.

That response then gets cached, and will return the <p>pending</p> response until it expires.
Suffixing a ?1 to the URL to bypass the URL caching then results in being able to access it.

Steps to R

• Add code examples for each sniff. Done
• Show how to run individual sniffs or exclude individual sniffs.
• For each sniff show how to customize if applicable.
• Explain why, benefits of why you'd want each sniff.

Remove scipy from How To Create Development Environments step 4 "Add dependencies" in doc/how_to_sprint.rst That is, only install numpy (specific version) as a dependency.