Add --silent option to ng build, test and lint
- Dominant language
- TypeScript
- Stars
- 27k
- Forks
- 11.8k
- Avg merge
- 14h 23m
- Merged PRs (30d)
- 162
Description
# 🚀 Feature request
Add a `--silent` option to **build**, **test** and **lint** so that it only outputs errors.
### Command (mark with an `x`)
- [ ] new
- [x] build
- [ ] serve
- [x] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [x] lint
- [ ] extract-i18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
### Description
So the usecase for us is that we have a pre-push GIT hook that runs **lint**, **test** and **build** before allowing the push to go through. Our issue is that we have a rather large application and the output for test and build are quite massive. An ideal situation would be if neither of the commands output anything if they pass and only show the errors if they don't.
Another usecase where this could be useful is for PR-builds to deliver a small but relevant report.
### Describe the solution you'd like
Add a `--silent` option that only output any potential error the command might come across.
### Describe alternatives you've considered
_Optionally:_ Add a `--loglevel` option so you could filter away depending on the level of your choice.
Contributor guide
Research direction
Start at the ng build, ng test, and ng lint command entry points and inspect how their output is currently emitted. Define done as a --silent option supported by all three commands that suppresses output on success while retaining errors, with command coverage confirming the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100