rumdl 0.0.64__tar.gz → 0.0.65__tar.gz

{rumdl-0.0.64 → rumdl-0.0.65}/Cargo.lock

@@ -1704,7 +1704,7 @@ dependencies = [
 
 [[package]]
 name = "rumdl"
-version = "0.0.64"
+version = "0.0.65"
 dependencies = [
  "anyhow",
  "assert_cmd",

{rumdl-0.0.64 → rumdl-0.0.65}/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "rumdl"
-version = "0.0.64"
+version = "0.0.65"
 edition = "2021"
 description = "A fast Markdown linter written in Rust (Ru(st) MarkDown Linter)"
 authors = ["Ruben J. Jongejan <ruben.jongejan@gmail.com>"]

{rumdl-0.0.64 → rumdl-0.0.65}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rumdl
-Version: 0.0.64
+Version: 0.0.65
 Classifier: Development Status :: 4 - Beta
 Classifier: Environment :: Console
 Classifier: Intended Audience :: Developers

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md002.md

@@ -11,7 +11,7 @@ description: Ensures the first heading in a document is a top-level heading (h1)
 
 ## Description
 
-This rule ensures that the first heading in a document is a top-level heading (h1). Using a top-level heading  
+This rule ensures that the first heading in a document is a top-level heading (h1). Using a top-level heading
 as the first heading helps establish the document's main topic and maintains proper document structure.
 
 ## Configuration
@@ -32,8 +32,6 @@ Example configuration:
 
 ## Examples
 
-<!-- markdownlint-disable -->
-
 ### Valid
 
 ```markdown
@@ -48,6 +46,8 @@ Example configuration:
 
 ### Invalid
 
+<!-- rumdl-disable MD002 -->
+
 ```markdown
 ## Document Title
 
@@ -56,6 +56,8 @@ Example configuration:
 # Main Heading
 ```
 
+<!-- rumdl-enable MD002 -->
+
 ### Fixed
 
 ```markdown
@@ -68,6 +70,8 @@ Example configuration:
 
 ### Special Cases
 
+<!-- rumdl-disable MD002 -->
+
 ```markdown
 ### Third Level Heading
 
@@ -81,7 +85,8 @@ Heading
 Heading
 =======
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD002 -->
 
 ## Rationale
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md003.md

@@ -34,7 +34,6 @@ Example configuration:
 }
 ```
 
-<!-- markdownlint-disable -->
 ## Examples
 
 ### ✓ Correct (ATX Style)
@@ -65,6 +64,8 @@ Second Level Heading
 
 ### ❌ Incorrect (Mixed Styles)
 
+<!-- rumdl-disable MD003 -->
+
 ```markdown
 # First Level Heading
 
@@ -73,7 +74,8 @@ Second Level Heading
 
 ### Third Level Heading
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD003 -->
 
 ## Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md005.md

@@ -18,7 +18,8 @@ This rule has no configuration options. It enforces:
 - 0 spaces for top-level list items
 - 2 spaces per level for nested items (both ordered and unordered lists)
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD005 -->
+
 ## Examples
 
 ### Valid
@@ -98,7 +99,8 @@ This rule has no configuration options. It enforces:
 1. Ordered item at same level
 2. Another ordered item
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD005 -->
 
 ## Related Rules
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md006.md

@@ -12,7 +12,8 @@ Using proper indentation helps clearly distinguish between top-level list items
 
 This rule has no configurable options. It always enforces that top-level list items start at the beginning of the line.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD006 -->
+
 ## Examples
 
 ### Valid
@@ -62,6 +63,7 @@ This is invalid because all top-level list items are indented with 2 spaces. The
 The rule will automatically fix incorrectly indented top-level list items by removing the leading whitespace:
 
 Before:
+
 ```markdown
   * Item 1
   * Item 2
@@ -70,6 +72,7 @@ Before:
 ```
 
 After:
+
 ```markdown
 * Item 1
 * Item 2
@@ -92,7 +95,8 @@ Some text here
   * Indented list 1  <!-- This is an error -->
   * Indented list 2  <!-- This is an error -->
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD006 -->
 
 The second list would trigger warnings because the items are indented.
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md007.md

@@ -10,7 +10,8 @@ Nested list items should be indented with exactly 2 spaces per level. This ensur
 
 ## Examples
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD007 -->
+
 ### Valid
 
 ```markdown
@@ -40,7 +41,8 @@ Nested list items should be indented with exactly 2 spaces per level. This ensur
 * Item 2
   * Another nested item
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD007 -->
 
 ## Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md009.md

@@ -14,7 +14,8 @@ Trailing whitespace can cause issues with some Markdown parsers and is generally
 
 ## Examples
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD009 -->
+
 ### Valid
 
 ```markdown
@@ -35,7 +36,8 @@ And this one too
 This line has no trailing spaces
 And this one is fixed too
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD009 -->
 
 ### Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md010.md

@@ -14,7 +14,8 @@ leading to inconsistent rendering.
 
 ## Examples
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD010 -->
+
 ### Valid
 
 ```markdown
@@ -38,7 +39,8 @@ leading to inconsistent rendering.
   * Indented with spaces
     * Deeper indentation
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD010 -->
 
 ### Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md011.md

@@ -13,7 +13,8 @@ This rule has no configurable options. It simply identifies and fixes reversed l
 
 ## Examples
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD011 -->
+
 ### Valid
 
 ```markdown
@@ -32,7 +33,8 @@ These links follow the correct Markdown syntax, with text in square brackets fol
 [Contact us](mailto:example@example.com)
 ```
 
-In these examples, the link syntax is reversed, with text in parentheses and the URL in square brackets. This is incorrect Markdown syntax and will not render as a proper link in most Markdown processors.
+In these examples, the link syntax is reversed, with text in parentheses and the URL in square brackets. This is incorrect Markdown syntax and will not render as a proper link in most Markdown
+processors.
 
 ### Fixed
 
@@ -43,7 +45,8 @@ When running the linter with fixes applied, the above invalid links would be tra
 [Documentation](./docs/README.md)
 [Contact us](mailto:example@example.com)
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD011 -->
 
 ## Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md013.md

@@ -15,7 +15,8 @@ Lines in the Markdown document should not exceed a certain length. This helps wi
 
 ## Examples
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD013 -->
+
 ### Valid
 
 ```markdown
@@ -36,7 +37,8 @@ This is a very long line that exceeds the maximum line length limit and will tri
 This is a line that has been broken up
 to stay under the maximum line length limit.
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD013 -->
 
 ## Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md014.md

@@ -12,7 +12,8 @@ When documenting shell commands, it's helpful to show their output to provide co
 
 ## Examples
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD014 -->
+
 ### Valid
 
 ```markdown
@@ -45,7 +46,7 @@ $ ls -l
 ```
 
 $ echo "Hello"
-<!-- markdownlint-enable -->
+<!-- rumdl-enable MD014 -->
 
 ```text
 ```

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md018.md

@@ -5,7 +5,8 @@
 This rule ensures that there is a space between the hash signs (#) and the heading text in ATX-style headings.
 A missing space can cause inconsistent rendering across different Markdown processors.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD018 -->
+
 ## Examples
 
 ### Valid
@@ -40,7 +41,8 @@ A missing space can cause inconsistent rendering across different Markdown proce
 ##### Heading 5
 ###### Heading 6
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD018 -->
 
 ## Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md019.md

@@ -5,7 +5,8 @@
 This rule ensures that there is only one space between the hash signs (#) and the heading text in ATX-style headings.
 Multiple spaces can cause inconsistent rendering across different Markdown processors.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD019 -->
+
 ## Examples
 
 ### Valid
@@ -40,7 +41,8 @@ Multiple spaces can cause inconsistent rendering across different Markdown proce
 ##### Heading 5
 ###### Heading 6
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD019 -->
 
 ## Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md020.md

@@ -5,7 +5,8 @@
 This rule ensures that there is a space between the hash signs (#) and the heading text in closed ATX-style headings.
 A missing space can cause inconsistent rendering across different Markdown processors.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD020 -->
+
 ## Examples
 
 ### Valid
@@ -40,7 +41,8 @@ A missing space can cause inconsistent rendering across different Markdown proce
 ##### Heading 5 #####
 ###### Heading 6 ######
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD020 -->
 
 ## Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md021.md

@@ -5,7 +5,8 @@
 This rule ensures that there is only one space between the hash signs (#) and the heading text in closed ATX-style headings.
 Multiple spaces can cause inconsistent rendering across different Markdown processors.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD021 -->
+
 ## Examples
 
 ### Valid
@@ -40,7 +41,8 @@ Multiple spaces can cause inconsistent rendering across different Markdown proce
 ##### Heading 5 #####
 ###### Heading 6 ######
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD021 -->
 
 ## Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md022.md

@@ -10,7 +10,7 @@ Consistent spacing around headings improves readability and ensures proper rende
 - `lines_above`: Number of blank lines that should be above headings (default: 1)
 - `lines_below`: Number of blank lines that should be below headings (default: 1)
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD022 -->
 ## Examples
 
 ### Valid
@@ -55,7 +55,8 @@ More content here.
 
 Even more content.
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD022 -->
 
 ## Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md023.md

@@ -5,7 +5,8 @@
 This rule ensures that all headings start at the beginning of the line, without any indentation.
 Indented headings can cause inconsistent rendering across different Markdown processors.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD023 -->
+
 ## Examples
 
 ### Valid
@@ -31,7 +32,8 @@ Indented headings can cause inconsistent rendering across different Markdown pro
 ## Heading 2
 ### Heading 3
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD023 -->
 
 ## Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md024.md

@@ -8,7 +8,8 @@ Duplicate headings can confuse readers and cause issues with generated tables of
 By default, this rule considers all headings in the document, but it can be configured to  
 only check for duplicates within the same section level.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD024 -->
+
 ## Examples
 
 ### Valid
@@ -52,7 +53,8 @@ Some content here.
 
 More content here.
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD024 -->
 
 ## Configuration
 
@@ -67,7 +69,8 @@ the document hierarchy) are checked for duplicates. Default is `false`.
 
 MD024 does not support auto-fixing.
 
-Duplicate headings are only reported as warnings; no automatic fix is provided. This is because removing or changing headings automatically could result in data loss or confusion. Please review and resolve duplicate headings manually.
+Duplicate headings are only reported as warnings; no automatic fix is provided. This is because removing or changing headings automatically could result in data loss or confusion. Please review and
+resolve duplicate headings manually.
 
 ## Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md026.md

@@ -6,7 +6,6 @@ This rule ensures that headings do not end with punctuation characters. Trailing
 
 By default, this rule checks for the following punctuation characters: `.,;:!?`. The list of punctuation characters can be customized through configuration.
 
-<!-- markdownlint-disable -->
 ## Examples
 
 ### Valid
@@ -21,6 +20,8 @@ By default, this rule checks for the following punctuation characters: `.,;:!?`.
 
 ### Invalid
 
+<!-- rumdl-disable MD026 -->
+
 ```markdown
 # Introduction!
 
@@ -29,6 +30,8 @@ By default, this rule checks for the following punctuation characters: `.,;:!?`.
 ### How to Install.
 ```
 
+<!-- rumdl-enable MD026 -->
+
 ### Fixed
 
 ```markdown
@@ -38,7 +41,6 @@ By default, this rule checks for the following punctuation characters: `.,;:!?`.
 
 ### How to Install
 ```
-<!-- markdownlint-enable -->
 
 ## Configuration
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md027.md

@@ -6,7 +6,8 @@ This rule ensures that blockquote markers (`>`) are followed by a single space.
 Multiple spaces after the blockquote symbol can lead to inconsistent rendering and  
 are generally considered poor style.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD027 -->
+
 ## Examples
 
 ### Valid
@@ -32,7 +33,8 @@ are generally considered poor style.
 > Each line now starts with a single space after the '>' symbol.
 > This ensures consistent formatting.
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD027 -->
 
 ## Special Cases
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md028.md

@@ -10,7 +10,8 @@ rendering across different Markdown processors.
 
 This rule has no configuration options.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD028 -->
+
 ## Examples
 
 ### Valid
@@ -41,7 +42,8 @@ This rule has no configuration options.
 > that used to have a blank line
 > inside it, but now it's fixed.
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD028 -->
 
 ## Special Cases
 
@@ -55,6 +57,9 @@ This rule has no configuration options.
 **Blank lines between blockquotes**: rumdl only flags empty blockquote lines (lines with `>` but no content) that create breaks within blockquotes. markdownlint also flags plain blank lines that separate what it considers to be parts of the same logical blockquote. rumdl's approach is more conservative and avoids false positives where users intentionally separate different blockquotes.
 
 Example that markdownlint flags but rumdl doesn't:
+
+<!-- rumdl-disable MD028 -->
+
 ```markdown
 > First blockquote
 
@@ -62,12 +67,15 @@ Example that markdownlint flags but rumdl doesn't:
 ```
 
 rumdl treats these as two separate, valid blockquotes, while markdownlint suggests they should be:
+
 ```markdown
 > First blockquote
 >
 > Second blockquote
 ```
 
+<!-- rumdl-enable MD028 -->
+
 ## Related Rules
 
 - [MD027 - Multiple spaces after blockquote symbol](md027.md): Ensures proper blockquote formatting

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md029.md

@@ -7,7 +7,8 @@ list items should either all use the same number (usually 1) or use ascending nu
 
 Consistent list formatting improves readability and prevents confusion when lists are rendered.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD029 -->
+
 ## Examples
 
 ### Valid (ordered style)
@@ -41,7 +42,8 @@ Consistent list formatting improves readability and prevents confusion when list
 2. Second item
 3. Third item
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD029 -->
 
 ## Configuration
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md030.md

@@ -10,7 +10,8 @@ one space after the list marker.
 
 Consistent spacing improves readability and ensures proper rendering across different Markdown processors.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD030 -->
+
 ## Examples
 
 ### Valid
@@ -42,7 +43,8 @@ Consistent spacing improves readability and ensures proper rendering across diff
 1. Ordered list item with one space
 2. Another item with one space
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD030 -->
 
 ## Configuration
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md031.md

@@ -2,46 +2,47 @@
 
 ## Description
 
-This rule ensures that fenced code blocks are surrounded by blank lines. Adding blank lines before and after  
+This rule ensures that fenced code blocks are surrounded by blank lines. Adding blank lines before and after
 fenced code blocks improves readability and ensures proper rendering across different Markdown processors.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD031 MD040 MD022 -->
+
 ## Examples
 
 ### Valid
 
-```markdown
+````markdown
 Text before the code block.
 
-```markdown
+```
 Code block content
 ```
 
 Text after the code block.
-```
+````
 
 ### Invalid
 
-```markdown
+````markdown
 Text before the code block.
-```markdown
+```
 Code block content
 ```
 Text after the code block.
-```
+````
 
 ### Fixed
 
-```markdown
+````markdown
 Text before the code block.
 
-```markdown
+```
 Code block content
 ```
 
 Text after the code block.
-```
-<!-- markdownlint-enable -->
+````
+<!-- rumdl-enable MD031 MD040 MD022 -->
 
 ## Configuration
 

{rumdl-0.0.64 → rumdl-0.0.65}/docs/md032.md

@@ -8,7 +8,8 @@ improves readability and ensures proper rendering across different Markdown proc
 Without blank lines, lists might not be properly recognized as lists, especially when they follow
 paragraphs or other content.
 
-<!-- markdownlint-disable -->
+<!-- rumdl-disable MD032 -->
+
 ## Examples
 
 ### Valid
@@ -44,7 +45,8 @@ Text before the list.
 
 Text after the list.
 ```
-<!-- markdownlint-enable -->
+
+<!-- rumdl-enable MD032 -->
 
 ## Special Cases
 
@@ -58,6 +60,7 @@ Text after the list.
 **Mixed list markers**: rumdl treats consecutive list items with different markers (-, *, +) as a single list with inconsistent markers, flagged by MD004. markdownlint treats them as separate lists requiring blank lines between each marker change. rumdl's approach is more semantically correct as users typically intend this as one list with inconsistent styling.
 
 Example that markdownlint flags but rumdl doesn't:
+
 ```markdown
 - First item
 * Second item  ← markdownlint wants blank line before this