microsoft / microsoft/vscode-makefile-tools
`makefile.preConfigureScript` start folder
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 242
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I've a problem telling makefile extension where to find preConfigureScript. More precisely, I've figure out experimentally, that it is relative to the file in which makefile.preConfigureScript setting is specified, for example:
- If defined in .vscode/settings.json:, .vscode folder is used as a root folder for relative paths.
- If defined in X.code-workspace
settingsgroup: ,code-workspace folder is used as a root folder for relative paths. - Standard
${workspaceFolder}is not supported in settings.json.
As this is always a struggle (where VSCode is putting workspace settings - sometimes in .vscode/settings.json, sometimes in .code-workspace), can the extension docs be a bit more precise about how the extension resolve the path?
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
Review the extension documentation for makefile.preConfigureScript and verify the behavior described for .vscode/settings.json and an X.code-workspace settings group. Document the relative-path roots and whether ${workspaceFolder} is supported, so users can determine the resolved folder from their settings location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100