Several file extension pattern
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 596
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
Hi, most of implementation globs has such pattern:
some/path/*.{txt,ts,rs}
How could I get something like that? Or maybe we could get it as new feature?
For example: https://github.com/mrmlnc/fast-glob
src/**/*.{css,scss} — matches all files in the src directory (any level of nesting) that have the .css or .scss extension.
file-[[:digit:]].js — matches files: file-0.js, file-1.js, …, file-9.js.
file-{1..3}.js — matches files: file-1.js, file-2.js, file-3.js.
file-(1|2) — matches files: file-1.js, file-2.js.
It would be great to improve this. Because we have a lot of new staff to build JS where is this patterns is standard and uses a lot of where.
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
Start by reading the repository’s current glob-pattern syntax and matching entry point, then compare its behavior with the requested brace, character-class, range, and alternation forms. Define which forms are in scope and verify completion with focused matching cases for each supported form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100