Skip to content

bug(schematics): themingApi missing from schematics #23871

Open
@ghost

Description

Ever since this commit, we can no longer run the themingApi schematic outside of ng update. This means that if you have a codebase with just scss, you will no longer be able to convert to ng12. One use-case is that you have a theme in its own repository or module, and import it in the projects where you need it.

So my proposal is: bring it back. I don't see any reason to remove it as a standalone schematic, given its usefulness.

If bringing it back is a problem, then it should at least be removed from the documentation. I spent several hours trying to figure out where this darn themingApi is at.

I think it makes more sense to just read the above description, but here's the template stuff:

Reproduction

Steps to reproduce:

  1. make a project with just @angular/material^12
  2. run ng g @angular/material:themingApi

Expected Behavior

Angular CLI converts the scss to new style, as advertised here.

Actual Behavior

Error:

An unhandled exception occurred: Schematic "themingApi" not found in collection "@angular/material".

Environment

  • Angular: n/a
  • CDK/Material: 12.0.0-rc3 and above
  • Browser(s): n/a
  • Operating System (e.g. Windows, macOS, Ubuntu): Windows 10

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentarea: ng-generateSchematics that generate code in user projectsarea: ng-updateIssues related to `ng-update` integrationarea: theming

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions