microsoft / microsoft/vscode-cpptools
`yarn build` should run `yarn install` and `generate-native-strings`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
yarn build needs to be the single command that brings the project up to date. Currently, if some packages are not installed, or the string table has changed, just doing a yarn build may result in a failure to build, or, worse, a build that reports incorrect log output or crashes, due to the TypeScript side of the native string localization system not having been updated. These two operations (and any others that I may have overlooked (generate-options-schema?) that are similarly necessary) should be done by yarn build and not rely on the user to know they need to be performed separately. (Maybe yarn build should call yarn prep?)
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
Inspect the scripts behind yarn build, yarn install, generate-native-strings, and possibly generate-options-schema or yarn prep. Determine which preparation steps are required before a reliable build; done means a single yarn build updates dependencies and generated localization data before building.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100