Config: Flatten .herb.yml structure and add rule-level patterns#755
Merged
Config: Flatten .herb.yml structure and add rule-level patterns#755
.herb.yml structure and add rule-level patterns#755Conversation
.herb.yml structure and add rule-level include.herb.yml structure and add rule-level patterns
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request restructures the
.herb.ymlschema to use a flat structure for linter and formatter file patterns, moving from the nestedfiles.patterns/exclude/extensionsformat to a simplerfiles.include/excludeformat.The change also introduces new
include,exclude, andonlyoptions for rule-level configuration, allowing rules to specify additional file patterns in an additive manner similar to tool-level includes.The rule pattern system now supports three distinct configuration options with clear precedence rules. When
onlyis specified, it restricts the rule to those specific patterns and ignores anyincludesettings. Whenonlyis absent butincludeis present, the rule applies only to files matching the include patterns. Theexcludeoption is always applied regardless of other pattern settings.