Progress indication for schematics

Open
#12,479 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
angular, typescript
Domain
cli, tooling

Research direction

Start by tracing the TSLintFixTask used during ng update and review how schematics currently report activity. Define the scope for a configurable progress indicator and the broader schematic status reporting described in the issue; done should make long-running fixes visibly active and identify the running schematic when possible.

Written by the indexing model from the issue text.

Description

area: @angular-devkit/schematics area: @angular/cli feature feature: votes required ng update DX

Since the TSLintFixTask can take a lot of time (e.g. if used to apply source code transformations for ng-update), it would be nice to have a progress indicator that shows that "something" actually runs.

For example: if someone runs ng update @angular/material@next, it's not clear for a period of time that the fix task actually "runs". See: https://github.com/angular/material2/issues/12774.

An option that can be specified when configuring the TSlintFixTask would be nice to have. The option would then show a simple progress indicator while TSLint runs.

Ideally there would be a way for a schematic to:

  • Have an progress-spinner with a name of the schematic currently running
  • Report a status (similar to how Bazel repository_ctx can report statuses)

Nowadays a lot of schematics need to run as part of an ng update and it would be helpful to know what schematic currently runs / what it currently does (if known)

cc. @jelbourn

Dominant language
TypeScript
Stars
27k
Forks
11.8k
Avg merge
16h 35m
Merged PRs (30d)
176

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from angular/angular-cli

All issues in angular/angular-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.