Skip to content

Commit

Permalink
fix(website): missing colon before tip notes in configs.md (#4982)
Browse files Browse the repository at this point in the history
* fix(website): missing colon before tip notes in configs.md

* fix: new issue template too
  • Loading branch information
JoshuaKGoldberg committed May 16, 2022
1 parent 4a500b2 commit f3a1aba
Showing 1 changed file with 4 additions and 4 deletions.
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.

0 comments on commit f3a1aba

Please sign in to comment.