phpcs

Project description

Behind the scenes, a side-project has started to create a (GitHub Pages) website for this project with helpful information about the things PHPCompatibility detects and how to fix them.

@afilina has done amazing work creating a documentation generation engine which will create a page with the basic information about each sniff from the docblocks in the sniff code itsel

What problem would the enhancement address for VIP?

There's a potential issue with using target="_blank" and not using rel="noopener" or rel="noreferrer".
See: https://web.dev/external-anchors-use-rel-noopener/

Describe the solution you'd like

Maybe warn about this if we see noopener or noreferrer present?

What code should be reported as a violation?

`<a target="_

when cs2pr completes and no errors/warnings have to be emitted, the screen stays empty.

as a user I dont know whether everything worked well and nothing had to be reported or there was a error and I dont see it.

at best we could emit a processed x errors and y warnings or similar status message at the very end into STDERR, so we dont destory possible consumers of our gihtub-api checks

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

PHP_CodeSniffer v3.1.1 changed the search order for configuration files, we need to update to follow here.

It appears that there's no link to, or information about, the PHPCS rules from anywhere on the Coding Standards Handbook.