mathisonian / mathisonian/command-exists
commandExists should return boolean instead of rejecting
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 147
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Unless there was an error with checking if the command exists. It would make more sense and be more idiomatic to have a resolve(true/false) rather than rejecting in the case of the command not existing. This also means you can use async/await syntax: `const exists = await commandExists('the-command')`
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 at the commandExists entry point and inspect how the promise handles a missing command versus an actual checking error. Verify that a missing command resolves to true or false for async/await callers, while genuine checking errors still reject; add or update tests if the repository provides them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100