fix: validate rules and recursive check globs - #22
Merged
Conversation
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.
Summary
*,?, and recursive**inputs deterministically while enforcing that every pattern matchesVerification
npm run release:checkgit diff --check origin/main..HEADCommit-by-commit changes
fix: validate rules and expand recursive globs— adds schema checks and deterministic recursive file discoverytest: cover rules validation and recursive globs— adds unit and CLI regression coveragedocs: define rules and glob validation— documents supported syntax, constraints, and error behaviorRisk Level
Notes: Invalid rules and unmatched literal inputs now fail earlier with stable diagnostics, matching the documented strict-input contract.
Rollback Plan
Human Decision Needed