You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: refactor config discovery and severity handling
Simplified config discovery which uses git and cwd boundaries only:
- Remove project markers (Cargo.toml, package.json, go.mod, etc.) as boundaries
- Keep only git repositories (.git) as meaningful boundaries for config search
- Add current working directory as boundary for CLI mode
- Update ConfigDiscovery struct to track current working directory
- Maintain workspace root boundaries for LSP integration
- Update README.md to reflect new simpler boundary detection strategy
- Remove obsolete test for Cargo.toml boundary detection
- Fix CLI integration test naming for consistency
Fix the bug, when the violations printed with WARN severity instead of
ERR:
- The `print_cli_errors` function in `quickmark-cli` now directly uses the severity from the `RuleViolation` struct, instead of looking it up from the configuration. This simplifies the code and makes it more robust.
- The `MultiRuleLinter` in `quickmark-core` now injects the correct severity into each `RuleViolation` as it is created.
- The test for `print_cli_errors` has been updated to reflect these changes and now uses the `MultiRuleLinter` to generate violations with the correct severities.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+16-10Lines changed: 16 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -211,42 +211,48 @@ QuickMark uses a sophisticated hierarchical configuration discovery system that
211
211
212
212
#### Hierarchical Configuration Discovery
213
213
214
-
QuickMark automatically discovers configuration files by searching upward from the target markdown file's directory, stopping at natural project boundaries. This enables different parts of your project to have their own linting rules while maintaining a sensible inheritance hierarchy.
214
+
QuickMark automatically discovers configuration files by searching upward from the target markdown file's directory, stopping at repository boundaries. This enables different parts of your project to have their own linting rules while maintaining a sensible inheritance hierarchy.
215
215
216
216
**Search Process:**
217
217
218
218
- Starts from the directory containing the target markdown file
219
219
- Searches upward through parent directories for `quickmark.toml` files
220
220
- Uses the first configuration file found
221
-
- Stops searching when it encounters project boundary markers
221
+
- Stops searching when it encounters boundary markers
222
222
223
-
**Project Boundary Markers** (search stops at these):
0 commit comments