microsoft / microsoft/vscode-cpptools
Config provider API to provide all configurations upfront (as well as indicate which sources are 'active').
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
This is based on the discussion here: https://github.com/microsoft/vscode-cmake-tools/issues/1875
Ultimately, Unification may require that we modify how custom configuration providers work, so all configurations are provided up front. Configurations for all files are needed by EdgeSystem to build the include graph (amoung other reasons). Regarding https://github.com/microsoft/vscode-cmake-tools/issues/1875 , included in those configurations could be an indication of which project (build target) is currently active. Source selection for header files could use that information to prefer sources from the current active configuration.
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
Read the linked vscode-cmake-tools discussion and the existing custom configuration provider API. Determine how configurations for all files and active-project metadata should be represented; done means an agreed API contract that supports upfront configuration data and active-source selection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100