mesonbuild / mesonbuild/vscode-meson
The extension does not check whenever meson is in PATH
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 138
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Attempting to run any extension command without meson in PATH environment variable results in a error ('configure' and 'reconfigure') or results in no response ('build').
runMesonConfigure in meson/runners.ts lacks in any protection clauses against this case.
IMO The extension should check and warn the user whenever meson doesn't exist in PATH.
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 in src/meson/runners.ts at runMesonConfigure, then trace the configure, reconfigure, and build commands that invoke it. Reproduce the behavior with meson absent from PATH. Done means the extension checks for meson and warns the user instead of failing silently or producing an unhandled error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100