Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(website): missing colon before tip notes in configs.md #4982

Merged
merged 2 commits into from May 16, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/linting/CONFIGS.md
Expand Up @@ -40,7 +40,7 @@ These rules are those whose reports are almost always for a bad practice and/or
}
```

::tip
:::tip
We strongly recommend all TypeScript projects extend from this configuration.
:::

Expand All @@ -58,7 +58,7 @@ Rules in this configuration are similarly useful to those in `recommended`.
}
```

::tip
:::tip
We recommend all TypeScript projects extend from this configuration, with the caveat that rules using type information take longer to run.
See [Linting with Type Information](/docs/linting/type-linting) for more details.
:::
Expand All @@ -77,7 +77,7 @@ Additional strict rules that can also catch bugs but are more opinionated than r
}
```

::tip
:::tip
We recommend a TypeScript project extend from this configuration only if a nontrivial percentage of its developers are highly proficient in TypeScript.
:::

Expand All @@ -89,4 +89,4 @@ See [ESLint's Configuring Rules docs](https://eslint.org/docs/user-guide/configu

### Suggesting Configuration Changes

If you feel strongly that a specific rule should (or should not) be one of these configurations, please feel free to [file an issue](TODO: NEW ISSUE TEMPLATE) along with a **detailed** argument explaining your reasoning.
If you feel strongly that a specific rule should (or should not) be one of these configurations, please feel free to [file an issue](https://github.com/typescript-eslint/typescript-eslint/issues/new/choose) along with a **detailed** argument explaining your reasoning.