Skip to content

docs: fix backslashes in fluent builder example - #102

Open
dajiaohuang wants to merge 1 commit into
dazinator:developfrom
dajiaohuang:docs/fix-readme-builder-20261016
Open

dajiaohuang wants to merge 1 commit into
dazinator:developfrom
dajiaohuang:docs/fix-readme-builder-20261016

Conversation

@dajiaohuang

Copy link
Copy Markdown

Summary

Fixes #92.

The fluent builder adds one backslash path separator, but the README passes a verbatim C# string containing two backslashes to IsMatch. The example therefore returns false, contrary to its comment.

Use a single backslash in both the displayed glob pattern and the verbatim subject string. No runtime behavior changes.

Validation

  • Reproduced the original example returning false against current develop source.
  • Confirmed the corrected example returns true and glob.ToString() equals the corrected displayed pattern.
  • Ran a bounded public-API probe against current source: 89 checks passed covering README matching/escaping, string/span, fluent construction, formatting, options, and match/nonmatch generation.
  • CRLF-aware whitespace check passed.

The probe used .NET 10 with SPAN enabled and isolated local configuration/cache paths; the repository's pinned .NET 8 SDK is not installed here. The full upstream test suite, legacy target frameworks and benchmarks were not run. This is a documentation-only change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

README fluent builder example is wrong

1 participant