@alexlit/lint-kit 112.3.2 → 112.3.4

package/packages/config-markdownlint/node_modules/markdownlint/doc/md051.md

@@ -1,87 +0,0 @@
-# `MD051` - Link fragments should be valid
-
-Tags: `links`
-
-Aliases: `link-fragments`
-
-Fixable: Some violations can be fixed by tooling
-
-This rule is triggered when a link fragment does not match any of the fragments
-that are automatically generated for headings in a document:
-
-```markdown
-# Heading Name
-
-[Link](#fragment)
-```
-
-To fix this issue, change the link fragment to reference an existing heading's
-generated name (see below):
-
-```markdown
-# Heading Name
-
-[Link](#heading-name)
-```
-
-Link fragments may be handled case-sensitively, so this rule requires fragments
-to exactly match the [GitHub heading algorithm][github-heading-algorithm].
-Therefore, the following example is reported as a violation:
-
-```markdown
-# Heading Name
-
-[Link](#Heading-Name)
-```
-
-Alternatively, some platforms allow the syntax `{#named-anchor}` to be used
-within a heading to provide a specific name (consisting of only lower-case
-letters, numbers, `-`, and `_`):
-
-```markdown
-# Heading Name {#custom-name}
-
-[Link](#custom-name)
-```
-
-Alternatively, any HTML tag with an `id` attribute or an `a` tag with a `name`
-attribute can be used to define a fragment:
-
-```markdown
-<a id="bookmark"></a>
-
-[Link](#bookmark)
-```
-
-An `a` tag can be useful in scenarios where a heading is not appropriate or for
-control over the text of the fragment identifier.
-
-This rule also recognizes the custom fragment syntax used by GitHub to highlight
-[specific content in a document][github-linking-to-content].
-
-For example, this link to line 20:
-
-```markdown
-[Link](#L20)
-```
-
-And this link to content starting within line 19 running into line 21:
-
-```markdown
-[Link](#L19C5-L21C11)
-```
-
-Rationale: [GitHub section links][github-section-links] are created
-automatically for every heading when Markdown content is displayed on GitHub.
-This makes it easy to link directly to different sections within a document.
-However, section links change if headings are renamed or removed. This rule
-helps identify broken section links within a document.
-
-Section links are **not** part of the CommonMark specification. This rule
-enforces the [GitHub heading algorithm][github-heading-algorithm] which is:
-convert heading to lowercase, remove punctuation, convert spaces to dashes,
-append an incrementing integer as needed for uniqueness.
-
-[github-section-links]: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#section-links
-[github-heading-algorithm]: https://github.com/gjtorikian/html-pipeline/blob/f13a1534cb650ba17af400d1acd3a22c28004c09/lib/html/pipeline/toc_filter.rb
-[github-linking-to-content]: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown#linking-to-markdown

package/packages/config-markdownlint/node_modules/markdownlint/doc/md052.md

@@ -1,40 +0,0 @@
-# `MD052` - Reference links and images should use a label that is defined
-
-Tags: `images`, `links`
-
-Aliases: `reference-links-images`
-
-Parameters:
-
-- `shortcut_syntax`: Include shortcut syntax (`boolean`, default `false`)
-
-Links and images in Markdown can provide the link destination or image source
-at the time of use or can define it elsewhere and use a label for reference.
-The reference format is convenient for keeping paragraph text clutter-free
-and makes it easy to reuse the same URL in multiple places.
-
-There are three kinds of reference links and images:
-
-```markdown
-Full: [text][label]
-Collapsed: [label][]
-Shortcut: [label]
-
-Full: ![text][image]
-Collapsed: ![image][]
-Shortcut: ![image]
-
-[label]: https://example.com/label
-[image]: https://example.com/image
-```
-
-A link or image renders correctly when the corresponding label is defined, but
-displays as text with brackets when the label is not present. By default, this
-rule warns of undefined labels for "full" and "collapsed" reference syntax but
-not for "shortcut" syntax because it is ambiguous.
-
-The text `[example]` could be a shortcut link or the text "example" in brackets,
-so "shortcut" syntax is ignored by default. To include "shortcut" syntax, set
-the `include_shortcut` parameter to `true`. Note that doing so produces warnings
-for *all* text in the document that *could* be a shortcut. If bracketed text is
-intentional, brackets can be escaped with the `\` character: `\[example\]`.

package/packages/config-markdownlint/node_modules/markdownlint/doc/md053.md

@@ -1,38 +0,0 @@
-# `MD053` - Link and image reference definitions should be needed
-
-Tags: `images`, `links`
-
-Aliases: `link-image-reference-definitions`
-
-Parameters:
-
-- `ignored_definitions`: Ignored definitions (`string[]`, default `["//"]`)
-
-Fixable: Some violations can be fixed by tooling
-
-Links and images in Markdown can provide the link destination or image source
-at the time of use or can use a label to reference a definition elsewhere in
-the document. The latter reference format is convenient for keeping paragraph
-text clutter-free and makes it easy to reuse the same URL in multiple places.
-
-Because link and image reference definitions are located separately from
-where they are used, there are two scenarios where a definition can be
-unnecessary:
-
-1. If a label is not referenced by any link or image in a document, that
-   definition is unused and can be deleted.
-2. If a label is defined multiple times in a document, the first definition is
-   used and the others can be deleted.
-
-This rule considers a reference definition to be used if any link or image
-reference has the corresponding label. The "full", "collapsed", and "shortcut"
-formats are all supported.
-
-If there are reference definitions that are deliberately unreferenced, they can
-be ignored by setting the `ignored_definitions` parameter. The default value of
-this parameter ignores the following convention for adding non-HTML comments to
-Markdown:
-
-```markdown
-[//]: # (This behaves like a comment)
-```

package/packages/config-markdownlint/node_modules/markdownlint/doc/md054.md

@@ -1,100 +0,0 @@
-# `MD054` - Link and image style
-
-Tags: `images`, `links`
-
-Aliases: `link-image-style`
-
-Parameters:
-
-- `autolink`: Allow autolinks (`boolean`, default `true`)
-- `collapsed`: Allow collapsed reference links and images (`boolean`, default
-  `true`)
-- `full`: Allow full reference links and images (`boolean`, default `true`)
-- `inline`: Allow inline links and images (`boolean`, default `true`)
-- `shortcut`: Allow shortcut reference links and images (`boolean`, default
-  `true`)
-- `url_inline`: Allow URLs as inline links (`boolean`, default `true`)
-
-Fixable: Some violations can be fixed by tooling
-
-Links and images in Markdown can provide the link destination or image source at
-the time of use or can use a label to reference a definition elsewhere in the
-document. The three reference formats are convenient for keeping paragraph text
-clutter-free and make it easy to reuse the same URL in multiple places.
-
-By default, this rule allows all link/image styles.
-
-Setting the `autolink` parameter to `false` disables autolinks:
-
-```markdown
-<https://example.com>
-```
-
-Setting the `inline` parameter to `false` disables inline links and images:
-
-```markdown
-[link](https://example.com)
-
-![image](https://example.com)
-```
-
-Setting the `full` parameter to `false` disables full reference links and
-images:
-
-```markdown
-[link][url]
-
-![image][url]
-
-[url]: https://example.com
-```
-
-Setting the `collapsed` parameter to `false` disables collapsed reference links
-and images:
-
-```markdown
-[url][]
-
-![url][]
-
-[url]: https://example.com
-```
-
-Setting the `shortcut` parameter to `false` disables shortcut reference links
-and images:
-
-```markdown
-[url]
-
-![url]
-
-[url]: https://example.com
-```
-
-To fix violations of this rule, change the link or image to use an allowed
-style. This rule can automatically fix violations when a link or image can be
-converted to the `inline` style (preferred) or a link can be converted to the
-`autolink` style (which does not support images and must be an absolute URL).
-This rule does *not* fix scenarios that require converting a link or image to
-the `full`, `collapsed`, or `shortcut` reference styles because that involves
-naming the reference and determining where to insert it in the document.
-
-Setting the `url_inline` parameter to `false` prevents the use of inline links
-with the same absolute URL text/destination and no title because such links can
-be converted to autolinks:
-
-```markdown
-[https://example.com](https://example.com)
-```
-
-To fix `url_inline` violations, use the simpler autolink syntax instead:
-
-```markdown
-<https://example.com>
-```
-
-Rationale: Consistent formatting makes it easier to understand a document.
-Autolinks are concise, but appear as URLs which can be long and confusing.
-Inline links and images can include descriptive text, but take up more space in
-Markdown form. Reference links and images can be easier to read and manipulate
-in Markdown form, but require a separate link reference definition.

package/packages/config-markdownlint/node_modules/markdownlint/doc/md055.md

@@ -1,54 +0,0 @@
-# `MD055` - Table pipe style
-
-Tags: `table`
-
-Aliases: `table-pipe-style`
-
-Parameters:
-
-- `style`: Table pipe style (`string`, default `consistent`, values
-  `consistent` / `leading_and_trailing` / `leading_only` /
-  `no_leading_or_trailing` / `trailing_only`)
-
-This rule is triggered when a [GitHub Flavored Markdown table][gfm-table-055]
-is inconsistent about its use of leading and trailing pipe characters (`|`).
-
-By default (`consistent` style), the header row of the first table in a document
-is used to determine the style that is enforced for all tables in that document.
-A specific style can be required by setting the `style` parameter accordingly.
-
-This table's header row has leading and trailing pipes, but its delimiter row is
-missing the trailing pipe and its first row of cells is missing the leading
-pipe:
-
-```markdown
-| Header | Header |
-| ------ | ------
-  Cell   | Cell   |
-```
-
-To fix these issues, make sure there is a pipe character at the beginning and
-end of every row:
-
-```markdown
-| Header | Header |
-| ------ | ------ |
-| Cell   | Cell   |
-```
-
-Note that text immediately following a table (i.e., not separated by an empty
-line) is treated as part of the table (per the specification) and may also
-trigger this rule:
-
-```markdown
-| Header | Header |
-| ------ | ------ |
-| Cell   | Cell   |
-This text is part of the table
-```
-
-Rationale: Some parsers have difficulty with tables that are missing their
-leading or trailing pipe characters. The use of leading/trailing pipes can also
-help provide visual clarity.
-
-[gfm-table-055]: https://github.github.com/gfm/#tables-extension-

package/packages/config-markdownlint/node_modules/markdownlint/doc/md056.md

@@ -1,37 +0,0 @@
-# `MD056` - Table column count
-
-Tags: `table`
-
-Aliases: `table-column-count`
-
-This rule is triggered when a [GitHub Flavored Markdown table][gfm-table-056]
-does not have the same number of cells in every row.
-
-This table's second data row has too few cells and its third data row has too
-many cells:
-
-```markdown
-| Header | Header |
-| ------ | ------ |
-| Cell   | Cell   |
-| Cell   |
-| Cell   | Cell   | Cell   |
-```
-
-To fix these issues, ensure every row has the same number of cells:
-
-```markdown
-| Header | Header |
-| ------ | ------ |
-| Cell   | Cell   |
-| Cell   | Cell   |
-| Cell   | Cell   |
-```
-
-Note that a table's header row and its delimiter row must have the same number
-of cells or it will not be recognized as a table (per specification).
-
-Rationale: Extra cells in a row are usually not shown, so their data is lost.
-Missing cells in a row create holes in the table and suggest an omission.
-
-[gfm-table-056]: https://github.github.com/gfm/#tables-extension-

package/packages/config-markdownlint/node_modules/markdownlint/helpers/LICENSE

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) David Anson
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.

package/packages/config-markdownlint/node_modules/markdownlint/helpers/README.md

@@ -1,72 +0,0 @@
-# markdownlint-rule-helpers
-
-> A collection of `markdownlint` helper functions for custom rules
-
-## Overview
-
-The [Markdown][markdown] linter [`markdownlint`][markdownlint] offers a variety
-of built-in validation [rules][rules] and supports the creation of [custom
-rules][custom-rules]. The internal rules share various helper functions; this
-package exposes those for reuse by custom rules.
-
-## API
-
-*Undocumented* - This package exports the internal functions as-is. The APIs
-were not originally meant to be public, are not officially supported, and may
-change from release to release. There are brief descriptive comments above each
-function, but no [JSDoc][jsdoc] annotations. That said, some of what's here will
-be useful to custom rule authors and may avoid duplicating code.
-
-## Examples
-
-### Using Helpers from a Custom Rule
-
-```javascript
-const { forEachLine, getLineMetadata } = require("markdownlint-rule-helpers");
-
-/** @type import("markdownlint").Rule */
-module.exports = {
-  "names": [ "every-n-lines" ],
-  "description": "Rule that reports an error every N lines",
-  "tags": [ "test" ],
-  "parser": "none",
-  "function": (params, onError) => {
-    const n = params.config.n || 2;
-    forEachLine(getLineMetadata(params), (line, lineIndex) => {
-      const lineNumber = lineIndex + 1;
-      if ((lineNumber % n) === 0) {
-        onError({
-          "lineNumber": lineNumber,
-          "detail": "Line number " + lineNumber
-        });
-      }
-    });
-  }
-};
-```
-
-### Applying Recommended Fixes
-
-```javascript
-const { "sync": markdownlintSync } = require("markdownlint");
-const markdownlintRuleHelpers = require("markdownlint-rule-helpers");
-
-function fixMarkdownlintViolations(content) {
-  const fixResults = markdownlintSync({ strings: { content } });
-  return markdownlintRuleHelpers.applyFixes(content, fixResults.content);
-}
-```
-
-See also: [`markdownlint` built-in rule implementations][lib].
-
-## Tests
-
-*None* - The entire body of code is tested to 100% coverage by the core
-`markdownlint` project, so there are no additional tests here.
-
-[custom-rules]: https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/CustomRules.md
-[jsdoc]: https://en.m.wikipedia.org/wiki/JSDoc
-[lib]: https://github.com/DavidAnson/markdownlint/tree/v0.34.0/lib
-[markdown]: https://en.wikipedia.org/wiki/Markdown
-[markdownlint]: https://github.com/DavidAnson/markdownlint
-[rules]: https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/Rules.md