Add `completed` event for stepper / steps

[olman21]

Bug, feature request, or proposal:

Proposal

What is the expected behavior?

Optionally allow the consumer define if it wants to auto-advance an step when it completes (by using [completed] step property)

What is the current behavior?

Nothing happens as soon the step is marked as completed

What is the use-case or motivation for changing an existing behavior?

Use Observable based state such as NgRx stores, and in a more functional way allow set the stepper navigation based on state, now I have to subscribe to store and call navigation via an stepper instance in order to handle steps advance, too imperatively and also results in a awful timing issues because when stepper.next() is called and [completed] property update is on its way nothing happens.

Is there anything else we should know?

I'm willing to implement such feature. No breaking changes would be introduced.

[josephperrott]

It seems reasonable and if it can be done in a non-breaking way I am sure we would welcome the contribution.

@mmalerba to confirm.

[mmalerba]

I assume you mean an output (completed) rather than an input [completed] correct? That seems like a reasonable feature to me

[jelbourn]

Updated this to clarify the feature we would add here: introducing a completed event for the stepper/steps so that the application could do whatever it wants upon completion.

[pkirchniawy]

Hej there! This would be my first issue but I would love to tackle it.

[mmalerba]

Sure, you can add me as a reviewer on your PR when you're ready

[ramprakashram]

@mmalerba If this issue is still open, I can take it up ?

[pkirchniawy]

Hej @ramprakashram I'm currently working on it :)

[ramprakashram]

Sure then @pkirchniawy

[angular-robot[bot]]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot[bot]]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

[synopss]

I assume you mean an output (completed) rather than an input [completed] correct? That seems like a reasonable feature to me

I think, the initial request was to use the already existing input [completed] value to ask to move to the next step if a new optional input [auto-advance] is enabled.

So, if [completed] is set to true, then the stepper will automatically move to the next step.

[jomendez]

I agree with @synopss, but also believe that the two use cases (exposing an event (completed) and creating an input [auto-avance]) could be very beneficial and shouldn't break existing functionality.

[naaajii]

~~I've created an PR for this request: #26817.~~

I've created an PR for this request: #26819. ( I messed up Google's CLA, was logged into wrong account. apologies! )

This is my first time contributing, please shed light if I have something wrong or missed out something.

[skilledDev96]

Is someone working on it? @naaajii you deleted your branch?

Can someone just clarify what is still needed as there is a few use cases proposed and the stepper has been Amended since issue was raised 6 years ago?