mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2025-09-21 21:30:47 +02:00
Add mention of using "extends" in .markdownlint.json to reference installed packages (closes #1555).
This commit is contained in:
parent
a9417fdf67
commit
a84f7c5b18
1 changed files with 6 additions and 6 deletions
12
README.md
12
README.md
|
@ -421,9 +421,9 @@ object.
|
|||
See [ValidatingConfiguration.md](schema/ValidatingConfiguration.md) for ways to
|
||||
use the JSON Schema to validate configuration.
|
||||
|
||||
For more advanced scenarios, styles can reference and extend other styles.
|
||||
The `readConfig` and `readConfigSync` functions can be used to read such
|
||||
styles.
|
||||
For more advanced scenarios, styles can reference and build upon other styles
|
||||
via the `extends` keyword and a file path or (installed) package name. The
|
||||
`readConfig` function can be used to read such aggregate styles from code.
|
||||
|
||||
For example, assuming a `base.json` configuration file:
|
||||
|
||||
|
@ -678,9 +678,9 @@ uses rule aliases (ex: `no-hard-tabs`) instead of names (ex: `MD010`).
|
|||
### Config
|
||||
|
||||
The `options.config` configuration object is simple and can be stored in a file
|
||||
for readability and easy reuse. The `readConfig` and `readConfigSync` functions
|
||||
load configuration settings and support the `extends` keyword for referencing
|
||||
other files (see above).
|
||||
for readability and easy reuse. The `readConfig` function loads configuration
|
||||
settings and supports the `extends` keyword for referencing files or packages
|
||||
(see above).
|
||||
|
||||
By default, configuration files are parsed as JSON (and named
|
||||
`.markdownlint.json`). Custom parsers can be provided to handle other formats
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue