microsoft / microsoft/vscode-makefile-tools
Allow users to define their own problem matchers
Open
Nobody has claimed this yet.
enhancement
Feature: problem-matchers
- Dominant language
- TypeScript
- Stars
- 242
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
As soon as https://github.com/microsoft/vscode/issues/61497 is implemented, with a small fix we can let our users to implement their own problem matchers, without a change in the package.json of Makefile Tools and an extension release update.
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 reviewing the linked VS Code issue 61497 and the extension's package.json configuration. Determine how user-defined problem matchers could work without changing Makefile Tools' package.json or requiring an extension release update. Done means users can define their own problem matchers under that constraint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100