mjackson / mjackson/broccoli-select
Make it OK for a excluded file to not be there
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
It appears that rejectFiles makes broccoli-select fail if no files are found to skip.
I think it would be better for the meaning of broccoli-select to mean "give me the files, except exclude any that match "abc*" ".... meaning that it is OK if those don't existing, just make sure they don't exist.
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 locating rejectFiles in broccoli-select and trace how it handles a glob that matches no files. Confirm the current failure with the repository's existing checks, then make exclusion patterns succeed when no matching files exist and verify that matching files are still excluded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100