From fae76b5b7d77ea3d5e31e69d134c4cc65e899cdb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=EB=A3=A8=EB=B0=80LuMir?= Date: Tue, 24 Dec 2024 18:09:19 +0900 Subject: [PATCH] docs: add missing backticks in various parts of the documentation --- docs/src/extend/plugins.md | 2 +- docs/src/rules/id-match.md | 2 +- docs/src/rules/no-array-constructor.md | 2 +- docs/src/rules/no-console.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/src/extend/plugins.md b/docs/src/extend/plugins.md index 592a41a3563b..65d5426d776b 100644 --- a/docs/src/extend/plugins.md +++ b/docs/src/extend/plugins.md @@ -40,7 +40,7 @@ If you plan to distribute your plugin as an npm package, make sure that the modu ### Meta Data in Plugins -For easier debugging and more effective caching of plugins, it's recommended to provide a name and version in a `meta` object at the root of your plugin, like this: +For easier debugging and more effective caching of plugins, it's recommended to provide a `name` and `version` in a `meta` object at the root of your plugin, like this: ```js const plugin = { diff --git a/docs/src/rules/id-match.md b/docs/src/rules/id-match.md index 3fbe3925d5d3..86ff85f904b7 100644 --- a/docs/src/rules/id-match.md +++ b/docs/src/rules/id-match.md @@ -9,7 +9,7 @@ rule_type: suggestion Naming things consistently in a project is an often underestimated aspect of code creation. When done correctly, it can save your team hours of unnecessary head scratching and misdirections. This rule allows you to precisely define and enforce the variables and function names on your team should use. -No more limiting yourself to camelCase, snake_case, PascalCase, or HungarianNotation. Id-match has all your needs covered! +No more limiting yourself to camelCase, snake_case, PascalCase, or HungarianNotation. `id-match` has all your needs covered! ## Rule Details diff --git a/docs/src/rules/no-array-constructor.md b/docs/src/rules/no-array-constructor.md index eff97dee776b..51152dcc0418 100644 --- a/docs/src/rules/no-array-constructor.md +++ b/docs/src/rules/no-array-constructor.md @@ -10,7 +10,7 @@ related_rules: Use of the `Array` constructor to construct a new array is generally discouraged in favor of array literal notation because of the single-argument pitfall and because the `Array` global may be redefined. The exception is when -the Array constructor is used to intentionally create sparse arrays of a +the `Array` constructor is used to intentionally create sparse arrays of a specified size by giving the constructor a single numeric argument. ## Rule Details diff --git a/docs/src/rules/no-console.md b/docs/src/rules/no-console.md index 9420c36ec03b..2887d31333be 100644 --- a/docs/src/rules/no-console.md +++ b/docs/src/rules/no-console.md @@ -69,7 +69,7 @@ console.error("Log an error level message."); If you're using Node.js, however, `console` is used to output information to the user and so is not strictly used for debugging purposes. If you are developing for Node.js then you most likely do not want this rule enabled. -Another case where you might not use this rule is if you want to enforce console calls and not console overwrites. For example: +Another case where you might not use this rule is if you want to enforce `console` calls and not `console` overwrites. For example: ```js /* eslint no-console: ["error", { allow: ["warn"] }] */ pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy