components
components copied to clipboard
bug(MatVerticalStepper): Can't bind to [animationDuration] in vertical stepper.
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
I'm unsure whether this is a bug or documentation error, but there's a whole section on it in the documentation here: https://material.angular.io/components/stepper/overview. I saw a lot of traffic on the issue on #17130, seems like it was pushed back in march, so I'm not sure why I am having the problem.
I have confirmed that I have ReactiveForms loaded as that seems to be a dependency according to StackOverflow.
Error message below:
Error: src/app/create-flow/create-flow.component.html:4:49 - error NG8002: Can't bind to 'animationDuration' since it isn't a known property of 'mat-vertical-stepper'.
1. If 'mat-vertical-stepper' is an Angular component and it has 'animationDuration' input, then verify that it is part of this module.
2. If 'mat-vertical-stepper' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message.
3. To allow any property add 'NO_ERRORS_SCHEMA' to the '@NgModule.schemas' of this component.
Reproduction
Copied example from documentation, ng serve
Expected Behavior
Runs as expected.
Actual Behavior
Fails on build.
Environment
@angular-devkit/architect 0.1303.9 @angular-devkit/build-angular 13.3.9 @angular-devkit/core 13.3.9 @angular-devkit/schematics 13.3.9 @angular/cdk 13.3.9 @angular/cli 13.3.9 @angular/fire 7.4.1 @angular/material 13.3.9 @schematics/angular 13.3.9 rxjs 7.5.6 typescript 4.6.4
This is likely an issue on your end since the vertical and horizontal steppers are on the same class: https://github.com/angular/components/blob/main/src/material/stepper/stepper.ts#L126
Closing due to inactivity.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.