1. The users of this style guide will probably expect that all of the rules that it prescribes will be enforced by eslint. However, this is not the case - there is a secret, non-documented segmentation where some rules are enforced and others are not, because they would be "too noisy on a legacy codebase". An example of a problematic rule like this is covered in issue #2020. I propose that all of

Given the immense popularity of Docker and the need to harden it different per platform (see ideas below) - we'd like to start writing a Docker best practices section.

You're welcome to contribute ideas and write best practices - writing and brainstorming will people is an amazing way to deepen your Docker understanding.

At first, we want to collect ideas for best practices, solidify a list

https://eslint.org/docs/rules/use-isnan

This is a proposal to modify the use-isnan rule.

Current rule setting:

use-isnan: "error"

Proposed rule setting:

["error", {"enforceForSwitchCase": true}]

The switch statement internally uses the === comparison to match the expression's value to a case clause.
Therefore, it can never match _case NaN. Also, `swit

Type of issue: (feature suggestion, bug?)

Suggestion

Chapter:

no-chapter

Why use .jsx instead of .js? It's not a best practice: facebook/create-react-app#87 (comment)

https://twitter.com/TheLarkInn/status/1056729742437543936
https://github.com/reactjs/rfcs/blob/gaearon-patch-2/text/0000-lazy.md

The README.md contains a lot of advanced config examples for functional tasks. We should probably add some basic ones as well:

1. '*.js': ['eslint'] <- fail when eslint finds issues issues
2. '*.js': ['eslint --fix', 'git add'] <- automatically fix eslint issues, and add to commit
3. '*.js': ['prettier --list-different'] <- fail when prettier finds issues
4. `'*.js': ['prettier --write

Since ESLint doesn't let us disable auto-fix for individual rules, and the capitalized-comments rule, while useful, can be annoying in editors when "auto-fix on save" is enabled.

SamVerschueren/vscode-linter-xo#78 (comment)

Tell us about your environment

• ESLint version: 5.9.0
• eslint-plugin-vue version: 6.1.2
• Node version: 10.13.0

Please show your full configuration:

/* example.ts */

// error: Parsing error: Unexpeced token, expected ":"
interface example {
  readonly id: string;
//         ^
}

/* .eslintrc */
{
  "root": true,
  "env": {
    "es6": true,
    "node": true,
    "jest/globals": true
  },
  "parser": "babel-eslint",
  "extends": [
    "eslint:recommended",
    "plugin:prettier/recommended",
    "plug

Vscode handles > in tags by calling html/tag and eventually closing the tag.

Example request:

[Trace - 7:58:44 AM] Sending request 'html/tag - (138)'. Params: { "textDocument": { "uri": "file:///home/kyoncho/Sources/lsp-docker/demo-projects/Scala/hello/src/test/scala/example/foo.html" }, "position": { "line": 0, "character": 6 } }

[Trace - 7:58:44 AM] Received response 'html/tag 

vscode中配置configFile,然后全局安装依赖模块

cnpm i eslint typescript @typescript-eslint/parser @typescript-eslint/eslint-plugin eslint-config-alloy -g

vscode配置文件如下：

"eslint.autoFixOnSave": true,
    "eslint.options": {
        "fix": true,
        "extensions": [
            ".js",
            ".ts",
            ".vue",
            ".html"
        ],
        "configFile": "/