Skip to content

Migrate ProgressSpinner to the Signals API (S) #2051

Open

Description

@geromegrignon

Part of #1971. Read the epic and packages/optimus-ui/.agents/skills/angular-signal-migration/SKILL.md in full before starting, and comment here to claim the issue.

Scope: packages/optimus-ui/src/progressspinner/ — 5 decorator input(s), 1 component class(es), ~123 lines. Size: S.

Also in this PR / notes:

  • Remove the deprecated styleClass input of ProgressSpinner (host class comes from the native class attribute) and extend the styleclass-to-class migration: add the selector(s) to MIGRATED_SELECTORS in packages/optimus-ui/schematics/migrations/styleclass-to-class/migration.ts, list them in migrations.json, add spec cases in schematics/test/styleclass-to-class.spec.ts. Then rewrite styleClass/[styleClass] usages in apps/docs.

Verify locally (only this scope, not the whole suite):

  • pnpm --filter @openng/optimus-ui test:unit -- --include progressspinner/progressspinner.test.ts
  • pnpm --filter @openng/optimus-ui test:schematics (you touched a migration)
  • pnpm exec prettier --check <changed files> and pnpm --filter @openng/optimus-ui build

PR: base next, title refactor(optimus-ui): progressspinner component migration to Signals API, link this issue with Closes #<this issue>.

Activity

  1. vitopio-prete commented on Nov 1, 2026

    @vitopio-prete

    PR is up: #2066

  2. added 2 commits that reference this issue on Nov 2, 2026
    051a6df
    facd937
  3. added a commit that references this issue on Nov 10, 2026
    c39e024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions