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
fix(konsistent): match variable-depth ** alongside {placeholder} and excludeFiles globs
Path matching required the pattern and matched path to have the same
number of segments when extracting placeholder values. This made any
`**` segment collapse to matching exactly one directory level whenever
the pattern also contained a `{placeholder}`, silently dropping
candidates at every other depth (#56).
`excludeFiles` entries hit the same equal-segment-count check, so a
`**/`-prefixed entry (as shown in docs/reference/configuration.md)
never matched and the file stayed in scope (#57).
Path segment matching now backtracks through candidate consumption
counts for `**`, so it can reconcile a variable-depth wildcard with
placeholder extraction and with plain excludeFiles glob patterns.
fix(konsistent): match variable-depth `**` alongside `{placeholder}` segments and glob-style `excludeFiles` patterns
7
+
8
+
`**` in a `paths` pattern next to a `{placeholder}` segment previously only matched a single intermediate directory level instead of every depth, because placeholder extraction required the pattern and path to have the same number of segments. `excludeFiles` entries prefixed with `**/` were silently ignored for the same reason. Path matching now backtracks through variable-depth `**` segments when extracting placeholders and when matching `excludeFiles` glob patterns, so both now behave as documented.
0 commit comments