microsoft / microsoft/terminal
Only regenerate our .metaproj when the .sln changes
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
From #2168.
This change could use some extra love - generating the metaproj takes a little while, as does parsing it. There might be a way to only generate the metaproj if it's changed, I didn't really investigate this, but presumably it could be done with a powershell script. I'll leave that for another work item in the future.
This is that future work item
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 locating the PowerShell script or build entry point that generates and parses the .metaproj, then identify how the .sln is tracked. Make generation conditional on changes to the solution and verify that the metaproj is not regenerated unnecessarily while still updating when the .sln changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, powershell
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100