-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stepper should provide an event handling for step changes #7259
Comments
You should be able to use the |
could you please tell us how to use it? there's no documentation as you said |
It's just an output on the stepper element. E.g. |
well I just want to move on the next step without that he does any sort of control. Something like:
|
The |
I tried selectedIndex as well.
But it complains:
|
This should be in the stepper documentation; library users shouldn't have to hunt around Github issues to figure out how to implement common use cases for components (like this one). It makes it seem like the developers haven't implemented the functionality, when in fact they have. |
selectionChanged is great for handling successful step changes. Is there a way to identify failed step change attempts? |
Looks like now it is selectionChange, notice there is no 'd' at the end. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug, feature request, or proposal:
Feature request
What is the expected behavior?
Add an event that gets triggered when the step changes in the stepper component
What is the current behavior?
There's no such event.
What are the steps to reproduce?
N/A
What is the use-case or motivation for changing an existing behavior?
I work on very dynamic apps. If the data shown in a step depends on the input of a previous step, there should be some event that informs that the step is being activated, so the data can be loaded.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 4.4.3
Angular material 2.0.0-beta.11
Typescript 2.3.4
Antergos Linux (rolling)
Chromium Browser 61
Is there anything else we should know?
N/A
The text was updated successfully, but these errors were encountered: