Skip to content

Commit

Permalink
docs: remove table of contents from markdown text
Browse files Browse the repository at this point in the history
  • Loading branch information
snitin315 committed Jun 14, 2022
1 parent f364d47 commit ae57021
Show file tree
Hide file tree
Showing 5 changed files with 0 additions and 25 deletions.
8 changes: 0 additions & 8 deletions docs/src/user-guide/configuring/configuration-files.md
Expand Up @@ -10,14 +10,6 @@ eleventyNavigation:

---

* [Configuration File Formats](#configuration-file-formats)
* [Using Configuration Files](#using-configuration-files)
* [Adding Shared Settings](#adding-shared-settings)
* [Cascading and Hierarchy](#cascading-and-hierarchy)
* [Extending Configuration Files](#extending-configuration-files)
* [Configuration Based on Glob Patterns](#configuration-based-on-glob-patterns)
* [Personal Configuration Files](#personal-configuration-files-deprecated)

## Configuration File Formats

ESLint supports configuration files in several formats:
Expand Down
6 changes: 0 additions & 6 deletions docs/src/user-guide/configuring/ignoring-code.md
Expand Up @@ -10,12 +10,6 @@ eleventyNavigation:

---

* [`ignorePatterns` in Config Files](#ignorepatterns-in-config-files)
* [The `.eslintignore` File](#the-eslintignore-file)
* [Using an Alternate File](#using-an-alternate-file)
* [Using eslintIgnore in package.json](#using-eslintignore-in-packagejson)
* [Ignored File Warnings](#ignored-file-warnings)

## `ignorePatterns` in Config Files

You can tell ESLint to ignore specific files and directories using `ignorePatterns` in your config files. `ignorePatterns` patterns follow the same rules as `.eslintignore`. Please see the [the `.eslintignore` file documentation](./ignoring-code#the-eslintignore-file) to learn more.
Expand Down
4 changes: 0 additions & 4 deletions docs/src/user-guide/configuring/language-options.md
Expand Up @@ -10,10 +10,6 @@ eleventyNavigation:

---

* [Specifying Environments](#specifying-environments)
* [Specifying Globals](#specifying-globals)
* [Specifying Parser Options](#specifying-parser-options)

## Specifying Environments

An environment provides predefined global variables. The available environments are:
Expand Down
4 changes: 0 additions & 4 deletions docs/src/user-guide/configuring/plugins.md
Expand Up @@ -10,10 +10,6 @@ eleventyNavigation:

---

* [Specifying Parser](#specifying-parser)
* [Specifying Processor](#specifying-processor)
* [Configuring Plugins](#configuring-plugins)

## Specifying Parser

By default, ESLint uses [Espree](https://github.com/eslint/espree) as its parser. You can optionally specify that a different parser should be used in your configuration file so long as the parser meets the following requirements:
Expand Down
3 changes: 0 additions & 3 deletions docs/src/user-guide/configuring/rules.md
Expand Up @@ -10,9 +10,6 @@ eleventyNavigation:

---

* [Configuring Rules](#configuring-rules)
* [Disabling Rules](#disabling-rules)

## Configuring Rules

ESLint comes with a large number of built-in rules and you can add more rules through plugins. You can modify which rules your project uses either using configuration comments or configuration files. To change a rule setting, you must set the rule ID equal to one of these values:
Expand Down

0 comments on commit ae57021

Please sign in to comment.