rumdl 0.0.139__tar.gz → 0.0.141__tar.gz

{rumdl-0.0.139 → rumdl-0.0.141}/CHANGELOG.md

@@ -7,6 +7,58 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.0.141] - 2025-09-15
+
+### Added
+
+- **MD013**: New normalize mode for combining short lines in paragraphs (related to #76)
+  - Added `reflow_mode` configuration with "default" and "normalize" options
+  - Normalize mode combines short lines to use the full configured line length
+  - Enables bulk removal of manual line breaks by setting high line_length with normalize mode
+  - Preserves markdown structure (lists, code blocks, tables, hard breaks)
+
+### Fixed
+
+- **MD013**: Fixed multi-line list item handling to avoid extra spaces when combining
+- **MD012**: Fixed line number reporting for EOF blank lines
+- **LSP**: Return null instead of empty array when no formatting available (related to #79)
+- **MD038**: Resolved false positives and added regression tests
+
+## [0.0.140] - 2025-09-11
+
+### Fixed
+
+- **LSP**: Support formatting documents without textDocument/didOpen (related to #79)
+  - Added lazy loading with disk fallback for unopened documents
+  - Editors like Helix can now format files without opening them first
+  - Implemented DocumentEntry structure to track document source and version
+  - Added intelligent caching for disk-loaded documents
+  - Maintains full compatibility with traditional LSP clients (VS Code)
+
+- **MD051**: Fixed false positives in large documents with multiline inline code spans
+  - Multiline inline code spans were incorrectly treated as code blocks
+  - This caused headings after line ~600 to not be detected properly
+  - Removed incorrect TOC detection logic that was causing issues
+
+- **MD032**: Fixed false positive for sequential ordered list continuations
+  - Sequential ordered list items (1., 2., 3.) no longer incorrectly flagged
+  - Added proper detection for list continuations vs separate lists
+  - Improved handling of lists interrupted by code blocks
+
+- **MD052**: Fixed false positive for literal brackets in backticks
+  - Text like `[from ...]` in inline code no longer flagged as broken reference
+  - Added workaround for multiline code span detection issues
+  - Properly distinguishes between literal text and reference links
+
+- **Documentation**: Added comprehensive inline configuration documentation
+  - Created detailed guide for rumdl-disable/enable comment syntax
+  - Documented all supported inline configuration formats
+  - Added examples for disabling rules per line, block, and file
+
+- **Fix Counting**: Corrected issue where unfixable warnings were counted as fixed
+  - MD013 warnings in table cells now correctly reported as unfixable
+  - Fix count now reflects actual fixes applied, not total warnings
+
 ## [0.0.139] - 2025-09-09
 
 ### Fixed
@@ -662,7 +714,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Initial implementation of remaining rules for markdownlint parity
 
-[Unreleased]: https://github.com/rvben/rumdl/compare/v0.0.138...HEAD
+[Unreleased]: https://github.com/rvben/rumdl/compare/v0.0.140...HEAD
+[0.0.140]: https://github.com/rvben/rumdl/compare/v0.0.139...v0.0.140
 [0.0.138]: https://github.com/rvben/rumdl/compare/v0.0.137...v0.0.138
 [0.0.137]: https://github.com/rvben/rumdl/compare/v0.0.136...v0.0.137
 [0.0.136]: https://github.com/rvben/rumdl/compare/v0.0.135...v0.0.136

{rumdl-0.0.139 → rumdl-0.0.141}/Cargo.lock

@@ -673,7 +673,7 @@ dependencies = [
  "cfg-if",
  "libc",
  "r-efi",
- "wasi 0.14.4+wasi-0.2.4",
+ "wasi 0.14.5+wasi-0.2.4",
 ]
 
 [[package]]
@@ -1625,7 +1625,7 @@ checksum = "caf4aa5b0f434c91fe5c7f1ecb6a5ece2130b02ad2a590589dda5146df959001"
 
 [[package]]
 name = "rumdl"
-version = "0.0.139"
+version = "0.0.141"
 dependencies = [
  "anyhow",
  "assert_cmd",
@@ -1879,9 +1879,9 @@ dependencies = [
 
 [[package]]
 name = "target-lexicon"
-version = "0.13.2"
+version = "0.13.3"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "e502f78cdbb8ba4718f566c418c52bc729126ffd16baee5baa718cf25dd5a69a"
+checksum = "df7f62577c25e07834649fc3b39fafdc597c0a3527dc1c60129201ccfcbaa50c"
 
 [[package]]
 name = "tempfile"
@@ -2175,9 +2175,9 @@ checksum = "10103c57044730945224467c09f71a4db0071c123a0648cc3e818913bde6b561"
 
 [[package]]
 name = "unicode-ident"
-version = "1.0.18"
+version = "1.0.19"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "5a5f39404a5da50712a4c1eecf25e90dd62b613502b7e925fd4e4d19b5c96512"
+checksum = "f63a545481291138910575129486daeaf8ac54aee4387fe7906919f7830c7d9d"
 
 [[package]]
 name = "unicode-normalization"
@@ -2263,9 +2263,18 @@ checksum = "ccf3ec651a847eb01de73ccad15eb7d99f80485de043efb2f370cd654f4ea44b"
 
 [[package]]
 name = "wasi"
-version = "0.14.4+wasi-0.2.4"
+version = "0.14.5+wasi-0.2.4"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "a4494f6290a82f5fe584817a676a34b9d6763e8d9d18204009fb31dceca98fd4"
+dependencies = [
+ "wasip2",
+]
+
+[[package]]
+name = "wasip2"
+version = "1.0.0+wasi-0.2.4"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "88a5f4a424faf49c3c2c344f166f0662341d470ea185e939657aaff130f0ec4a"
+checksum = "03fa2761397e5bd52002cd7e73110c71af2109aca4e521a9f40473fe685b0a24"
 dependencies = [
  "wit-bindgen",
 ]

{rumdl-0.0.139 → rumdl-0.0.141}/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "rumdl"
-version = "0.0.139"
+version = "0.0.141"
 edition = "2024"
 rust-version = "1.89.0"
 description = "A fast Markdown linter written in Rust (Ru(st) MarkDown Linter)"

{rumdl-0.0.139 → rumdl-0.0.141}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rumdl
-Version: 0.0.139
+Version: 0.0.141
 Classifier: Development Status :: 4 - Beta
 Classifier: Environment :: Console
 Classifier: Intended Audience :: Developers
@@ -674,6 +674,20 @@ rumdl import --dry-run .markdownlint.json
 
 For comprehensive documentation on global settings (file selection, rule enablement, etc.), see our [Global Settings Reference](docs/global-settings.md).
 
+### Inline Configuration
+
+rumdl supports inline HTML comments to disable or configure rules for specific sections of your Markdown files. This is useful for making exceptions without changing global configuration:
+
+```markdown
+<!-- rumdl-disable MD013 -->
+This line can be as long as needed without triggering the line length rule.
+<!-- rumdl-enable MD013 -->
+```
+
+Note: `markdownlint-disable`/`markdownlint-enable` comments are also supported for compatibility with existing markdownlint configurations.
+
+For complete documentation on inline configuration options, see our [Inline Configuration Reference](docs/inline-configuration.md).
+
 ### Configuration File Example
 
 Here's an example `.rumdl.toml` configuration file:

{rumdl-0.0.139 → rumdl-0.0.141}/README.md

@@ -645,6 +645,20 @@ rumdl import --dry-run .markdownlint.json
 
 For comprehensive documentation on global settings (file selection, rule enablement, etc.), see our [Global Settings Reference](docs/global-settings.md).
 
+### Inline Configuration
+
+rumdl supports inline HTML comments to disable or configure rules for specific sections of your Markdown files. This is useful for making exceptions without changing global configuration:
+
+```markdown
+<!-- rumdl-disable MD013 -->
+This line can be as long as needed without triggering the line length rule.
+<!-- rumdl-enable MD013 -->
+```
+
+Note: `markdownlint-disable`/`markdownlint-enable` comments are also supported for compatibility with existing markdownlint configurations.
+
+For complete documentation on inline configuration options, see our [Inline Configuration Reference](docs/inline-configuration.md).
+
 ### Configuration File Example
 
 Here's an example `.rumdl.toml` configuration file:

rumdl-0.0.141/docs/inline-configuration.md

@@ -0,0 +1,254 @@
+# Inline Configuration Reference
+
+This document describes how to disable or configure rumdl rules using inline HTML comments within your Markdown files.
+
+## Overview
+
+rumdl supports inline configuration comments that allow you to disable rules for specific sections, lines, or entire files. This is useful when you need to make exceptions for specific content without
+changing your global configuration.
+
+## Supported Comment Formats
+
+rumdl uses its own comment prefix, with support for markdownlint comments for compatibility:
+
+- `<!-- rumdl-... -->` - Primary rumdl syntax
+- `<!-- markdownlint-... -->` - Supported for markdownlint compatibility
+
+## Basic Usage
+
+### Disable All Rules
+
+Disable all rules from a specific point until re-enabled:
+
+```markdown
+This text is linted normally.
+
+<!-- rumdl-disable -->
+This text is not linted at all.
+Rules violations here are ignored.
+<!-- rumdl-enable -->
+
+This text is linted again.
+```
+
+### Disable Specific Rules
+
+Disable only specific rules:
+
+```markdown
+Normal linting applies here.
+
+<!-- rumdl-disable MD013 MD033 -->
+This content can have long lines (MD013) and inline HTML (MD033).
+Other rules still apply.
+<!-- rumdl-enable MD013 MD033 -->
+
+Back to normal linting.
+```
+
+## Line-Specific Configuration
+
+### Disable for Current Line
+
+Disable rules for the line containing the comment:
+
+```markdown
+This is a really long line that would normally violate MD013 but it's allowed <!-- rumdl-disable-line MD013 -->
+
+This line is checked normally.
+```
+
+### Disable for Next Line
+
+Disable rules for the line following the comment:
+
+```markdown
+<!-- rumdl-disable-next-line MD013 -->
+This very long line is allowed to exceed the normal line length limit without triggering a warning.
+
+This line is checked normally.
+```
+
+### Prettier Compatibility
+
+For compatibility with Prettier, rumdl also supports:
+
+```markdown
+<!-- prettier-ignore -->
+This line won't be checked for any rules.
+```
+
+## File-Level Configuration
+
+### Disable for Entire File
+
+Place at the beginning of the file to disable rules for the entire document:
+
+```markdown
+<!-- rumdl-disable-file -->
+
+# This Document
+
+Nothing in this file will be linted.
+```
+
+Or disable specific rules for the entire file:
+
+```markdown
+<!-- rumdl-disable-file MD013 MD033 -->
+
+# This Document
+
+Long lines and inline HTML are allowed throughout this file.
+Other rules still apply.
+```
+
+### Configure Rules for File
+
+Configure specific rule settings for the entire file:
+
+```markdown
+<!-- rumdl-configure-file { "MD013": { "line_length": 120 } } -->
+
+# This Document
+
+This file uses a line length of 120 instead of the default.
+```
+
+## Advanced Features
+
+### Capture and Restore
+
+Save and restore the current configuration state:
+
+```markdown
+Normal rules apply here.
+
+<!-- rumdl-capture -->
+<!-- rumdl-disable MD013 MD033 -->
+
+Content with specific rules disabled.
+
+<!-- rumdl-restore -->
+
+Previous configuration state is restored.
+```
+
+## Examples
+
+### Example 1: Documentation with Code Examples
+
+```markdown
+# API Documentation
+
+The API follows standard REST conventions.
+
+<!-- rumdl-disable MD013 -->
+```bash
+curl -X POST <https://api.example.com/v1/users/create> -H "Authorization: Bearer very-long-token-that-would-normally-violate-line-length" -d '{"name": "John Doe"}'
+```
+
+<!-- rumdl-enable MD013 -->
+
+Regular documentation continues here.
+
+```text
+
+### Example 2: Tables with Long Content
+
+```markdown
+## Configuration Options
+
+<!-- rumdl-disable MD013 -->
+| Option | Description | Default | Example |
+|--------|-------------|---------|---------|
+| `authentication_token` | A very long description about authentication tokens in the system | `null` | `Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...` |
+<!-- rumdl-enable MD013 -->
+```
+
+### Example 3: HTML Content
+
+```
+
+```markdown
+# Dashboard
+
+<!-- rumdl-disable MD033 -->
+<div class="alert alert-warning">
+  <strong>Warning!</strong> This feature is experimental.
+</div>
+<!-- rumdl-enable MD033 -->
+
+Continue with regular Markdown content.
+```
+
+### Example 4: Generated Content
+
+```markdown
+<!-- rumdl-disable-file -->
+<!-- This file is auto-generated. Do not edit manually. -->
+
+# Generated API Reference
+
+[Auto-generated content that may not follow all linting rules]
+```
+
+## Important Notes
+
+1. **Comment Placement**: Comments must be on their own line (except for `disable-line`)
+2. **Code Blocks**: Comments inside code blocks are ignored and won't affect configuration
+3. **Case Insensitive**: Rule names are case-insensitive (MD013, md013, Md013 all work)
+4. **Specificity**: More specific configurations override general ones
+5. **Compatibility**: Both `rumdl` (primary) and `markdownlint` (for compatibility) prefixes work identically
+
+## Rule Names Reference
+
+When specifying rules in inline comments, use the rule ID (e.g., MD013, MD033). See the [Rules Reference](RULES.md) for a complete list of available rules.
+
+## Comparison with Global Configuration
+
+| Use Case | Inline Configuration | Global Configuration |
+|----------|---------------------|---------------------|
+| Temporary exceptions | ✅ Best choice | ❌ Too permanent |
+| File-specific rules | ✅ Good for few files | ✅ Better for many files |
+| Generated content | ✅ Use disable-file | ✅ Use exclude patterns |
+| Project-wide settings | ❌ Too scattered | ✅ Best choice |
+
+## Best Practices
+
+1. **Use sparingly**: Inline configuration should be the exception, not the rule
+2. **Document why**: Add a comment explaining why rules are disabled
+3. **Be specific**: Disable only the specific rules needed, not all rules
+4. **Re-enable quickly**: Re-enable rules as soon as the exception is no longer needed
+5. **Consider alternatives**: Before disabling a rule, consider if the content can be restructured
+
+Example with explanation:
+
+```markdown
+<!-- Disable MD013 for this command example as it cannot be wrapped -->
+<!-- rumdl-disable-next-line MD013 -->
+docker run -d --name myapp -p 8080:8080 -e DATABASE_URL=postgresql://user:pass@localhost:5432/db mycompany/myapp:latest
+
+Regular content continues here.
+```
+
+## Troubleshooting
+
+### Comments Not Working
+
+1. Ensure comments are on their own line (except for `disable-line`)
+2. Check that comments are not inside code blocks
+3. Verify correct spelling of command and rule names
+4. Make sure you're using either `rumdl` or `markdownlint` (for compatibility) prefix consistently
+
+### Rules Still Triggering
+
+1. Check if the rule is configured to ignore inline configuration (rare)
+2. Verify the comment appears before the content it should affect
+3. Ensure you're using the correct rule ID (check with `rumdl rule MD###`)
+
+## See Also
+
+- [Global Settings Reference](global-settings.md) - Configure rules globally
+- [Rules Reference](RULES.md) - Complete list of available rules
+- [Configuration Guide](../README.md#configuration) - General configuration documentation