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.

Sign up for GitHub

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

Jump to bottom

Docs: fix broken links in configuring/README.md #14046

Merged
merged 1 commit into from Jan 27, 2021
Merged

Docs: fix broken links in configuring/README.md #14046

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 5 additions & 5 deletions docs/user-guide/configuring/README.md
View file
Open in desktop
Expand Up @@ -3,7 +3,7 @@
ESLint is designed to be flexible and configurable for your use case. You can turn off every rule and run only with basic syntax validation or mix and match the bundled rules and your custom rules to fit the needs of your project. There are two primary ways to configure ESLint:

1. **Configuration Comments** - use JavaScript comments to embed configuration information directly into a file.
1. **Configuration Files** - use a JavaScript, JSON, or YAML file to specify configuration information for an entire directory and all of its subdirectories. This can be in the form of an [`.eslintrc.*`](./configuring-files#configuration-file-formats) file or an `eslintConfig` field in a [`package.json`](https://docs.npmjs.com/files/package.json) file, both of which ESLint will look for and read automatically, or you can specify a configuration file on the [command line](https://eslint.org/docs/user-guide/command-line-interface).
1. **Configuration Files** - use a JavaScript, JSON, or YAML file to specify configuration information for an entire directory and all of its subdirectories. This can be in the form of an [`.eslintrc.*`](./configuration-files.md#configuration-file-formats) file or an `eslintConfig` field in a [`package.json`](https://docs.npmjs.com/files/package.json) file, both of which ESLint will look for and read automatically, or you can specify a configuration file on the [command line](https://eslint.org/docs/user-guide/command-line-interface).

Here are some of the options that you can configure in ESLint:

Expand All @@ -22,9 +22,9 @@ All of these options give you fine-grained control over how ESLint treats your c
* [Using Configuration Files](./configuration-files.md#using-configuration-files)
* [Adding Shared Settings](./configuration-files.md#adding-shared-settings)
* [Cascading and Hierarchy](./configuration-files.md#cascading-and-hierarchy)
* [Extending Configuration Files](./configuring-files.md#extending-configuration-files)
* [Configuration Based on Glob Patterns](./configuration-files.md#configuration-based-on-glon-patterns)
* [Personal Configuration Files](./configuration-files.md#personal-configuration-files)
* [Extending Configuration Files](./configuration-files.md#extending-configuration-files)
* [Configuration Based on Glob Patterns](./configuration-files.md#configuration-based-on-glob-patterns)
* [Personal Configuration Files](./configuration-files.md#personal-configuration-files-deprecated)

[**Language Options**](language-options.md)

Expand All @@ -48,5 +48,5 @@ All of these options give you fine-grained control over how ESLint treats your c
* [`ignorePatterns` in Config Files](./ignoring-code.md#ignorepatterns-in-config-files)
* [The `.eslintignore` File](./ignoring-code.md#the-eslintignore-file)
* [Using an Alternate File](./ignoring-code.md#using-an-alternate-file)
* [Using eslintIgnore in package.json](./ignoring-code.md#using-eslintignore-in-package.json)
* [Using eslintIgnore in package.json](./ignoring-code.md#using-eslintignore-in-packagejson)
* [Ignored File Warnings](./ignoring-code.md#ignored-file-warnings)