Skip to content

bug(theme): schematic doesn't ask for error hex color #29969

Closed
@AnkitaSood

Description

@AnkitaSood

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

As of v18.2, a theme can be generated with a custom color with the following schematic:
ng generate @angular/material:m3-theme

The schematic then prompts for hex codes for primary, secondary, tertiary, neutral colors.

It auto generates an error code palette based on the primary hex provided. It doesn't prompt the user to enter their own error color.

Reproduction

StackBlitz link:
Steps to reproduce:

  1. Ensure app and material are on latest stable version - v18.2
  2. Run the schematic ng generate @angular/material:m3-theme to generate a custom theme.
  3. Notice that the schematic doesn't prompt to enter hex color to be used to represent the error color palette.

Expected Behavior

The schematic should prompt user to enter hex code that is used to represent the error color palette.

Actual Behavior

Schematic doesn't prompt to enter hex color to be used to represent the error color palette.

Environment

  • Angular: 18.2
  • CDK/Material: 18.2
  • Browser(s):
  • Operating System (e.g. Windows, macOS, Ubuntu):

Metadata

Metadata

Assignees

No one assigned

    Labels

    P4A relatively minor issue that is not relevant to core functionsarea: cdk/schematicscdk/schematics is *not* a public APIarea: theming

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions