@10up/eslint-plugin 中文文档教程

发布于 3年前 浏览 29 项目主页 更新于 3年前

ESLint Plugin

ESLint 插件,包括用于 WordPress 开发的配置和自定义规则。

Installation

安装模块

npm install @wordpress/eslint-plugin --save-dev

注意:此包需要 node 12.0.0 或更高版本,以及 npm 6.9.0 或更高版本。 它与旧版本不兼容。

Usage

要选择默认配置,请扩展您自己项目的 .eslintrc 文件:

{
    "extends": [ "plugin:@wordpress/eslint-plugin/recommended" ]
}

请参阅 有关可共享配置的 ESLint 文档 了解更多信息。

推荐 预设将包括管理 ES2015+ 环境的规则,并包括来自 的规则eslint-plugin-jsx-a11yeslint-plugin-react eslint-plugin-prettier 项目。 它还包括与 @typescript-eslint/eslint-plugin 的可选集成在项目中安装 typescript 包时激活。

对于想要退出 Prettier 的项目,还有 recommended-with-formatting 规则集。 它启用了本机 ESLint 代码格式化规则。

Rulesets

或者,您可以选择仅加入插件提供的更精细的规则集。 这些包括:

  • custom
  • es5
  • esnext
  • jsdoc
  • jsx-a11y
  • react
  • i18n
  • test-e2e
  • test-unit

例如,如果您的项目不使用 React,您可以考虑使用以下 extends 定义扩展项目中仅包含 ESNext 规则:

{
    "extends": [ "plugin:@wordpress/eslint-plugin/esnext" ]
}

这些规则可以附加使用,因此您可以扩展esnextcustom 规则集,但省略了 reactjsx-a11y 配置。

粒度规则集不会定义任何环境全局变量。 因此,如果您的项目需要它们,您将需要自己定义它们。

Rules

RuleDescriptionRecommended
data-no-store-string-literalsDiscourage passing string literals to reference data stores
dependency-groupEnforce dependencies docblocks formatting
is-gutenberg-pluginGoverns the use of the process.env.IS_GUTENBERG_PLUGIN constant
no-base-control-with-label-without-idDisallow the usage of BaseControl component with a label prop set but omitting the id property
no-unguarded-get-range-atDisallow the usage of unguarded getRangeAt calls
no-unsafe-wp-apisDisallow the usage of unsafe APIs from @wordpress/* packages
no-unused-vars-before-returnDisallow assigning variable values if unused before a return
react-no-unsafe-timeoutDisallow unsafe setTimeout in component
valid-sprintfEnforce valid sprintf usage
i18n-ellipsisDisallow using three dots in translatable strings
i18n-no-collapsible-whitespaceDisallow collapsible whitespace in translatable strings
i18n-no-placeholders-onlyPrevent using only placeholders in translatable strings
i18n-no-variablesEnforce string literals as translation function arguments
i18n-text-domainEnforce passing valid text domains
i18n-translator-commentsEnforce adding translator comments
i18n-no-flanking-whitespaceDisallow leading or trailing whitespace in translatable strings
i18n-hyphenated-rangeDisallow hyphenated numerical ranges in translatable strings

Legacy

如果您正在使用 WordPress 的 .jshintrc JSHint 配置,并且您想迈出迁移到等效的 ESLint 的第一步,也可以定义您自己项目的 .eslintrc文件为:

{
    "extends": [ "plugin:@wordpress/eslint-plugin/jshint" ]
}

Contributing to this package

这是一个独立的包,是古腾堡项目的一部分。 该项目被组织为一个 monorepo。 它由多个独立的软件包组成,每个软件包都有特定的用途。 此 monorepo 中的包发布到 npm 并由 WordPress 以及其他软件项目。

要了解更多关于为这个包或整个古腾堡做贡献的信息,请阅读项目的主要贡献者指南。



代码即诗歌。

ESLint Plugin

ESLint plugin including configurations and custom rules for WordPress development.

Installation

Install the module

npm install @wordpress/eslint-plugin --save-dev

Note: This package requires node 12.0.0 or later, and npm 6.9.0 or later. It is not compatible with older versions.

Usage

To opt-in to the default configuration, extend your own project's .eslintrc file:

{
    "extends": [ "plugin:@wordpress/eslint-plugin/recommended" ]
}

Refer to the ESLint documentation on Shareable Configs for more information.

The recommended preset will include rules governing an ES2015+ environment, and includes rules from the eslint-plugin-jsx-a11y, eslint-plugin-react, and eslint-plugin-prettier projects. It also includes an optional integration with @typescript-eslint/eslint-plugin that gets activated when the typescript package is installed in the project.

There is also recommended-with-formatting ruleset for projects that want to opt out from Prettier. It has the native ESLint code formatting rules enabled instead.

Rulesets

Alternatively, you can opt-in to only the more granular rulesets offered by the plugin. These include:

  • custom
  • es5
  • esnext
  • jsdoc
  • jsx-a11y
  • react
  • i18n
  • test-e2e
  • test-unit

For example, if your project does not use React, you could consider extending including only the ESNext rules in your project using the following extends definition:

{
    "extends": [ "plugin:@wordpress/eslint-plugin/esnext" ]
}

These rules can be used additively, so you could extend both esnext and custom rulesets, but omit the react and jsx-a11y configurations.

The granular rulesets will not define any environment globals. As such, if they are required for your project, you will need to define them yourself.

Rules

RuleDescriptionRecommended
data-no-store-string-literalsDiscourage passing string literals to reference data stores
dependency-groupEnforce dependencies docblocks formatting
is-gutenberg-pluginGoverns the use of the process.env.IS_GUTENBERG_PLUGIN constant
no-base-control-with-label-without-idDisallow the usage of BaseControl component with a label prop set but omitting the id property
no-unguarded-get-range-atDisallow the usage of unguarded getRangeAt calls
no-unsafe-wp-apisDisallow the usage of unsafe APIs from @wordpress/* packages
no-unused-vars-before-returnDisallow assigning variable values if unused before a return
react-no-unsafe-timeoutDisallow unsafe setTimeout in component
valid-sprintfEnforce valid sprintf usage
i18n-ellipsisDisallow using three dots in translatable strings
i18n-no-collapsible-whitespaceDisallow collapsible whitespace in translatable strings
i18n-no-placeholders-onlyPrevent using only placeholders in translatable strings
i18n-no-variablesEnforce string literals as translation function arguments
i18n-text-domainEnforce passing valid text domains
i18n-translator-commentsEnforce adding translator comments
i18n-no-flanking-whitespaceDisallow leading or trailing whitespace in translatable strings
i18n-hyphenated-rangeDisallow hyphenated numerical ranges in translatable strings

Legacy

If you are using WordPress' .jshintrc JSHint configuration and you would like to take the first step to migrate to an ESLint equivalent it is also possible to define your own project's .eslintrc file as:

{
    "extends": [ "plugin:@wordpress/eslint-plugin/jshint" ]
}

Contributing to this package

This is an individual package that's part of the Gutenberg project. The project is organized as a monorepo. It's made up of multiple self-contained software packages, each with a specific purpose. The packages in this monorepo are published to npm and used by WordPress as well as other software projects.

To find out more about contributing to this package or Gutenberg as a whole, please read the project's main contributor guide.



Code is Poetry.

    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
    原文