microsoft / microsoft/vscode-makefile-tools
warn about trailling space
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 242
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
I had this issue:
foo:
helm repo update foo
helm upgrade --install ccm-foo foo/ccm-foo \
--version 0.1.2 \XXXX
--namespace kube-system
But there was no "XXXX", but there were spaces.
I got a strange error:
Error: "helm upgrade" requires 2 arguments
It took me some time to understand that the trailing spaces after "--version 0.1.2 " where the root cause.
Please make this visible somehow in the makefile plugin of vscode.
New comers could waste hours with this confusing whitespace handling.
Contributor guide
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 reproducing the reported sample in the VS Code Makefile Tools extension, using the shown Makefile command with trailing spaces after the line-continuation backslash. Read the extension's Makefile parsing and diagnostic entry points to determine where whitespace can be surfaced; done means users receive a visible warning that identifies the trailing spaces and explains the resulting command failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100