ng build/serve --watch should have a switch to clear the screen before each rebuild #25699
Comments
angular-robot
bot
added
the
feature: votes required
|
This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list. You can find more details about the feature request process in our documentation. |
|
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends. Find more details about Angular's feature request process in our documentation. |
angular-robot
bot
removed
the
feature: votes required
|
Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage. We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package. You can find more details about the feature request process in our documentation. |
angular-robot
bot
added
the
feature: insufficient votes
|
Here is my upvote for this. |
|
Starting from version 17.1, pressing |
|
@alan-agius4 does |
|
|
|
But this is not much different than my current capability. I can already press CTRL+L to clear my screen as needed. The desired behavior is for it to automatically clear each time it begins to rebuild, without the need for user interaction. |
…cly cleaning the terminal screen during rebuilds
When setting `"clearScreen": true` to the appliction builder during rebuilds the terminimal screen will be cleaned.
```json
{
"projects": {
"my-app": {
"projectType": "application",
"root": "",
"sourceRoot": "src",
"architect": {
"build": {
"builder": "@angular-devkit/build-angular:application",
"options": {
"clearScreen": true
}
}
}
}
}
}
```
Closes angular#25699
…cally cleaning the terminal screen during rebuilds
When setting `"clearScreen": true` to the appliction builder during rebuilds the terminimal screen will be cleaned.
```json
{
"projects": {
"my-app": {
"projectType": "application",
"root": "",
"sourceRoot": "src",
"architect": {
"build": {
"builder": "@angular-devkit/build-angular:application",
"options": {
"clearScreen": true
}
}
}
}
}
}
```
Closes angular#25699
…cally cleaning the terminal screen during rebuilds
When setting `"clearScreen": true` to the appliction builder during rebuilds the terminimal screen will be cleaned.
```json
{
"projects": {
"my-app": {
"projectType": "application",
"root": "",
"sourceRoot": "src",
"architect": {
"build": {
"builder": "@angular-devkit/build-angular:application",
"options": {
"clearScreen": true
}
}
}
}
}
}
```
Closes angular#25699
…cally cleaning the terminal screen during rebuilds
When setting `"clearScreen": true` to the appliction builder during rebuilds the terminimal screen will be cleaned.
```json
{
"projects": {
"my-app": {
"projectType": "application",
"root": "",
"sourceRoot": "src",
"architect": {
"build": {
"builder": "@angular-devkit/build-angular:application",
"options": {
"clearScreen": true
}
}
}
}
}
}
```
Closes angular#25699
…cally cleaning the terminal screen during rebuilds
When setting `"clearScreen": true` to the appliction builder during rebuilds the terminimal screen will be cleaned.
```json
{
"projects": {
"my-app": {
"projectType": "application",
"root": "",
"sourceRoot": "src",
"architect": {
"build": {
"builder": "@angular-devkit/build-angular:application",
"options": {
"clearScreen": true
}
}
}
}
}
}
```
Closes angular#25699
…cally cleaning the terminal screen during rebuilds
When setting `"clearScreen": true` to the appliction builder during rebuilds the terminimal screen will be cleaned.
```json
{
"projects": {
"my-app": {
"projectType": "application",
"root": "",
"sourceRoot": "src",
"architect": {
"build": {
"builder": "@angular-devkit/build-angular:application",
"options": {
"clearScreen": true
}
}
}
}
}
}
```
Closes angular#25699
…cally cleaning the terminal screen during rebuilds
When setting `"clearScreen": true` to the appliction builder during rebuilds the terminimal screen will be cleaned.
```json
{
"projects": {
"my-app": {
"projectType": "application",
"root": "",
"sourceRoot": "src",
"architect": {
"build": {
"builder": "@angular-devkit/build-angular:application",
"options": {
"clearScreen": true
}
}
}
}
}
}
```
Closes angular#25699
…cally cleaning the terminal screen during rebuilds
When setting `"clearScreen": true` to the appliction builder during rebuilds the terminimal screen will be cleaned.
```json
{
"projects": {
"my-app": {
"projectType": "application",
"root": "",
"sourceRoot": "src",
"architect": {
"build": {
"builder": "@angular-devkit/build-angular:application",
"options": {
"clearScreen": true
}
}
}
}
}
}
```
Closes #25699
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Command
build, serve
Description
Reviving #21559, as I'd like to see the same thing implemented, to always have a clear view of what is actually an error and what has already been addressed. Without this it's very confusing to scroll back and forth to see where the last batch of errors are starting, and what was the output from the last build.
Description of #21559 below:
When I'm refactoring large code-base i revised folowing process:
i have ng serve running
i do some changes in bulk without save
save all
i stop the process
clear the console
then start the ng serve again
I'm doing this to see in isolation what I break, fixed what are new issues etc. So I can focus only on what is relevant
Describe the solution you'd like
it would be nice to have a switch to run ng serve which would clear console everytime it detects change
Describe alternatives you've considered
Currently I'm doing it manually - stopping the process, clearing console and starting ng serve again
The text was updated successfully, but these errors were encountered: