angular / angular/angular-cli

Progress indication for schematics

Offen
#12,479 3 Kommentare 2 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
area: @angular-devkit/schematics area: @angular/cli feature feature: votes required ng update DX
Vorherrschende Sprache
TypeScript
Sterne
27k
Forks
11.8k
Ø Merge
14 Std. 23 Min.
Gemergte PRs (30 T.)
162

Beschreibung

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

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
angular, typescript
Bereich
cli, tooling
Issue-Typ
Feature
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
30/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.