Wrong token list created for "foo/**"
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 595
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
With latest version 0.3.0 I've created the following pattern:
Pattern { original: "/archiv/", tokens: [AnyRecursiveSequence, Char('a'), Char('r'), Char('c'), Char('h'), Char('i'), Char('v'), Char('/'), AnyRecursiveSequence], is_recursive: true }
As you can see the token "Char('/')" is too much and calls to matches don't work as expected.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce parsing and matching for the pattern "/archiv/" described in the report, then trace how its token list is created. Confirm that the generated tokens do not include the extra Char('/') and that matching behaves as expected for this pattern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100