search

Elchi3 / mdn-doc-tests

:no_entry_sign: UNMAINTAINED :no_entry_sign: This used to check MDN docs against some tests and cleanup tasks while editing, but add-on SDK based add-ons are obsolete. Use https://github.com/mdn/doc-linter-webextension and https://github.com/mdn/doc-linter-rules instead.
Mozilla Public License 2.0
10 stars 8 forks source link

Syntax Classes not allowed? #233

Open bunnybooboo opened 7 years ago

bunnybooboo commented 7 years ago

Seems quite the standard, throughout the recent editorial review push I've done, for syntax boxes to specify, via the SYNTAX HIGHLIGHTER (using the standard MDN editor toolbar), the code language therein. Example: obvious benefits seen with an article of mixed code syntax.

When running the 'MDN Doc Tests' add-on, any highlighted code flags as an error. Helping clarify for the reader what they are looking at if navigating to the page in isolation, but causing mdn-doc-tests to flag it as invalid.

I can only find syntax styling guide reference which encourages highlighting Bash code. Doing so also flags an error, leaving me confused as to the standard expected, and purpose of this particular test.

IF the style guide is ambiguous: why these specific tests?

bunnybooboo commented 7 years ago

This example uses class .css and is not flagged as an error. As seen in all CSS docs.