Lines Matching +full:lint +full:- +full:cpp
3 This style guide helps us create organized and easy-to-read documentation. It
12 `lowercase-with-dashes.md`.
15 * Some files, such as top-level markdown files, are exceptions.
16 * Documents should be word-wrapped at 80 characters.
19 * Check changes to documentation with `make lint-md`.
26 * Use gender-neutral pronouns and gender-neutral plural nouns.
35 * Documents must start with a level-one heading.
41 * Use [language][]-aware fences. (<code>```js</code>)
45 | ------------- | ----------------- |
48 | C++ | `cpp` |
60 If one of your language-aware fences needs an info string that is not
62 [`remark-preset-lint-node`][].
66 is necessary, include it as an asset in `assets/code-examples` and link to
69 backslash-escaping: `\_`, `\*`, and ``\` ``.
75 <!--lint disable maximum-line-length remark-lint-->
77 <!--lint enable maximum-line-length remark-lint-->
84 <!--lint disable prohibited-strings remark-lint-->
87 <!-- lint enable prohibited-strings remark-lint-->
91 <!-- lint disable prohibited-strings remark-lint-->
95 <!-- lint enable prohibited-strings remark-lint-->
102 <!-- lint enable prohibited-strings remark-lint-->
110 [Javascript type]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Grammar_and_types#…
111 [Microsoft Writing Style Guide]: https://docs.microsoft.com/en-us/style-guide/welcome/
112 [`remark-preset-lint-node`]: https://github.com/nodejs/remark-preset-lint-node
114 [info string]: https://github.github.com/gfm/#info-string