pickier 0.1.67 → 0.1.69

package/dist/src/rules/markdown/reference-links-images.d.ts

@@ -1,14 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * MD052 - Reference links and images should use a label that is defined
- *
- * Only fires on explicit reference-style link/image syntax where the
- * intent is unambiguous: `[text][label]` or `![alt][label]`.
- *
- * Does NOT fire on bare `[text]` shortcut references, because those collide
- * with too many legitimate non-link uses: array literals, TypeScript tuples,
- * shell test expressions, JSON examples, citation markers, etc.
- *
- * Matches markdownlint MD052 behavior for explicit references only.
- */
-export declare const referenceLinksImagesRule: RuleModule;

package/dist/src/rules/markdown/required-headings.d.ts

@@ -1,5 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * MD043 - Required heading structure
- */
-export declare const requiredHeadingsRule: RuleModule;

package/dist/src/rules/markdown/single-title.d.ts

@@ -1,5 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * MD025 - Multiple top-level headings in the same document
- */
-export declare const singleTitleRule: RuleModule;

package/dist/src/rules/markdown/single-trailing-newline.d.ts

@@ -1,5 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * MD047 - Files should end with a single newline character
- */
-export declare const singleTrailingNewlineRule: RuleModule;

package/dist/src/rules/markdown/strong-style.d.ts

@@ -1,16 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * MD050 - Strong style
- *
- * Inline code spans are masked before anything is matched, the way its twin
- * `emphasis-style` already did. Without it a code span holding two double
- * underscores - `typeof __ctx === 'undefined' ? undefined : __ctx` is the real
- * case - reads as underscore-strong, so a document written entirely in
- * asterisks is reported as inconsistent on every `**bold**` after it.
- *
- * The warning was the harmless half. The fixer rewrote the same span into
- * `**ctx === 'undefined' ? undefined : **ctx`, which changes what the code
- * says - a formatter corrupting code it was asked to leave alone is a much
- * worse failure than a false positive.
- */
-export declare const strongStyleRule: RuleModule;

package/dist/src/rules/markdown/table-column-count.d.ts

@@ -1,5 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * MD056 - Table column count
- */
-export declare const tableColumnCountRule: RuleModule;

package/dist/src/rules/markdown/table-column-style.d.ts

@@ -1,5 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * MD060 - Table column style
- */
-export declare const tableColumnStyleRule: RuleModule;

package/dist/src/rules/markdown/table-pipe-style.d.ts

@@ -1,5 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * MD055 - Table pipe style
- */
-export declare const tablePipeStyleRule: RuleModule;

package/dist/src/rules/markdown/ul-indent.d.ts

@@ -1,14 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * MD007 - Unordered list indentation
- *
- * Tracks list-nesting context to correctly handle nested lists, including
- * lists nested inside ordered list items (where indentation must align
- * with the content after the ordered marker, e.g. 3 spaces after "1. ").
- *
- * Matches markdownlint MD007 behavior: only top-level unordered lists and
- * their descendants nested under other unordered lists are checked against
- * the fixed indent. Lists nested inside ordered items may use any indent
- * that aligns with the parent's content column.
- */
-export declare const ulIndentRule: RuleModule;

package/dist/src/rules/markdown/ul-style.d.ts

@@ -1,5 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * MD004 - Unordered list style
- */
-export declare const ulStyleRule: RuleModule;

package/dist/src/rules/shell/command-substitution.d.ts

@@ -1,6 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * SC2006: Use $(...) notation instead of legacy backtick `...` command substitution.
- * Backticks are harder to nest and read. $() is the modern POSIX-compliant alternative.
- */
-export declare const commandSubstitutionRule: RuleModule;

package/dist/src/rules/shell/consistent-case-terminators.d.ts

@@ -1,9 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * Enforce consistent placement of case statement terminators (;;).
- * Each case branch must end with ;; before the next pattern or the closing
- * `esac`. The rule walks the case body honoring nested block structure so
- * `)` characters inside `for ... done`, `while ... done`, `if ... fi`, and
- * `$(...)` subshells are not mistaken for the next case pattern.
- */
-export declare const consistentCaseTerminatorsRule: RuleModule;

package/dist/src/rules/shell/function-style.d.ts

@@ -1,6 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * Enforce consistent function declaration style in shell scripts.
- * Default: prefer `name() {` over `function name {` (POSIX-compatible).
- */
-export declare const functionStyleRule: RuleModule;

package/dist/src/rules/shell/heredoc-indent.d.ts

@@ -1,7 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * Recommend <<- (with tab stripping) for indented heredocs.
- * When a heredoc is inside a function or loop, using << requires the delimiter
- * to be at column 0, which breaks indentation flow.
- */
-export declare const heredocIndentRule: RuleModule;

package/dist/src/rules/shell/indent.d.ts

@@ -1,2 +0,0 @@
-import type { RuleModule } from '../../types';
-export declare const indentRule: RuleModule;

package/dist/src/rules/shell/keyword-spacing.d.ts

@@ -1,10 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * Enforce proper spacing around shell keywords.
- * Flags: `if(`, `then;cmd`, missing space after ; in control flow, etc.
- *
- * String/quote/expansion interiors are ignored via `maskShellStrings`, so
- * ANSI-C escape codes such as `$'\033[0;31m'` are not misread as having a
- * missing space after `;`.
- */
-export declare const keywordSpacingRule: RuleModule;

package/dist/src/rules/shell/no-broken-redirect.d.ts

@@ -1,7 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * SC2069: Detect broken redirect ordering.
- * `cmd 2>&1 > file` redirects stderr to original stdout (terminal), not the file.
- * Correct: `cmd > file 2>&1` or `cmd &> file` (bash).
- */
-export declare const noBrokenRedirectRule: RuleModule;

package/dist/src/rules/shell/no-cd-without-check.d.ts

@@ -1,6 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * SC2164: Use `cd ... || exit` or `cd ... || return` to handle cd failure.
- * If `cd` fails, subsequent commands run in the wrong directory.
- */
-export declare const noCdWithoutCheckRule: RuleModule;

package/dist/src/rules/shell/no-eval.d.ts

@@ -1,6 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * Disallow use of eval in shell scripts.
- * eval is dangerous because it re-parses its arguments, leading to code injection risks.
- */
-export declare const noEvalRule: RuleModule;

package/dist/src/rules/shell/no-exit-in-subshell.d.ts

@@ -1,7 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * SC2033: exit in subshell only exits the subshell, not the script.
- * Code like `(cd dir && exit 1)` won't stop the parent script.
- * Use return in functions, or restructure to avoid subshells.
- */
-export declare const noExitInSubshellRule: RuleModule;

package/dist/src/rules/shell/no-ls-parsing.d.ts

@@ -1,7 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * SC2012: Don't parse the output of ls.
- * ls output is not safe for parsing — filenames can contain newlines, spaces, and special chars.
- * Use globs, find, or stat instead.
- */
-export declare const noLsParsingRule: RuleModule;

package/dist/src/rules/shell/no-trailing-semicolons.d.ts

@@ -1,6 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * Disallow unnecessary trailing semicolons on simple commands.
- * In shell, semicolons separate commands on the same line but are unnecessary at end of line.
- */
-export declare const noTrailingSemicolonsRule: RuleModule;

package/dist/src/rules/shell/no-trailing-whitespace.d.ts

@@ -1,5 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * Disallow trailing whitespace in shell scripts.
- */
-export declare const noTrailingWhitespaceRule: RuleModule;

package/dist/src/rules/shell/no-useless-cat.d.ts

@@ -1,6 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * SC2002: Useless use of cat. Instead of `cat file | cmd`, use `cmd < file` or `cmd file`.
- * Avoids spawning an unnecessary process.
- */
-export declare const noUselessCatRule: RuleModule;

package/dist/src/rules/shell/no-variable-in-single-quotes.d.ts

@@ -1,7 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * SC2016: Expressions don't expand in single quotes.
- * Detects cases where $var or ${var} appears inside single quotes,
- * which likely indicates the author intended double quotes.
- */
-export declare const noVariableInSingleQuotesRule: RuleModule;

package/dist/src/rules/shell/operator-spacing.d.ts

@@ -1,11 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * Enforce spaces inside test bracket expressions [ ] and [[ ]].
- * Missing spaces cause syntax errors or incorrect behavior.
- *
- * The rule ignores `[` and `]` that appear inside strings (`'...'`, `"..."`,
- * `$'...'`), parameter expansions (`${arr[@]}`, `${arr[0]}`), command
- * substitutions (`$(...)`) and comments, so valid bash such as
- * `${CERTS[@]}` or ANSI-C escapes like `$'\033[0;31m'` are not flagged.
- */
-export declare const operatorSpacingRule: RuleModule;

package/dist/src/rules/shell/prefer-double-brackets.d.ts

@@ -1,6 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * SC2292: Prefer [[ ]] over [ ] for tests in bash/zsh.
- * [[ ]] is safer: no word splitting, no pathname expansion, supports && || and regex.
- */
-export declare const preferDoubleBracketsRule: RuleModule;

package/dist/src/rules/shell/prefer-printf.d.ts

@@ -1,6 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * SC2059/SC2086: Prefer printf over echo -e / echo -n.
- * echo behavior varies across shells and platforms; printf is portable and predictable.
- */
-export declare const preferPrintfRule: RuleModule;

package/dist/src/rules/shell/quote-variables.d.ts

@@ -1,2 +0,0 @@
-import type { RuleModule } from '../../types';
-export declare const quoteVariablesRule: RuleModule;

package/dist/src/rules/shell/set-options.d.ts

@@ -1,8 +0,0 @@
-import type { RuleModule } from '../../types';
-/**
- * Recommend using `set -euo pipefail` for safer script execution.
- * - set -e: Exit on error
- * - set -u: Error on undefined variables
- * - set -o pipefail: Pipe failures propagate
- */
-export declare const setOptionsRule: RuleModule;

package/dist/src/rules/shell/shebang.d.ts

@@ -1,2 +0,0 @@
-import type { RuleModule } from '../../types';
-export declare const shebangRule: RuleModule;