We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
CS/markdownlint: various whitespace fixes
CS/markdownlint: use fenced codeblocks everywhere This makes it easier to copy/paste updated output to the wiki docs.
Merge progress reporting sections When I created the new section about progress reporting on the "Reporting" page, I'd overlooked that the "Usage" page already contained a section on progress reporting. This commit now removes the section from the "Reporting" page again and merges some of the information which was contained in that section, into the information about progress reporting on the "Usage" page. Includes various tweaks and updates to the pre-existing information: * Make it explicit how progress reporting can be enabled. * Shorten the example output for progress. * Mention the name of the configuration option to enable progress reporting by default. * Refresh the example output for the verbose example.
Reporting: add section about progress reporting
Update sniff code vs error code + additional info about this in Reporting and Advanced Usage Refs: #319, #328 Co-authored-by: Joachim Noreiko <[email protected]>
Reporting: add note about caching vs Performance Report Related to #306
Reporting: fix typo
Add information about the new Performance report Ref: https://github.com/PHPCSStandards/PHP_CodeSniffer/pull/60
Add "back to top" links under each section ... on long pages which contain a table of contents.
Use highlighted blocks for important information Ref: https://github.com/orgs/community/discussions/16925
Updated Reporting (markdown)
Added docs for code report
Added junit report type + updated all report output for latest version
Added JSON report docs
Added TOC
Created Reporting (markdown)