[Stepper] Export useStepperContext

[pzi]

Pretty much a similar PR to #31021 except this one is targeting the StepperContext as opposed to the StepContext.

I believe this would close #31277 as it would then expose both contexts that @jedimonkey was looking for (note: I work on the same project as @jedimonkey).

Additional context:
We are using the StepperContext to grab the activeStep and compare it to stepContext.index to return 100 or 0 progress value for a LinearProgress component sitting in between steps.

• I have followed (at least) the PR section of the contributing guide.

[mui-bot]

Details of bundle changes

Generated by 🚫 dangerJS against 13ecf9d

[pzi]

@danilo-leal are you able to kick off or ask someone to kick off the workflows at least, please? 😬

[pzi]

@hbjORbj is it possible to get this looked at by someone @mui, please? or even just get the workflows kicked off, please?

[hbjORbj]

Hi. Thanks for opening the pull request.

I ran the workflows as you requested.

Many CI tests are failing, so please address them first. You will find this guide useful: https://github.com/mui/material-ui/blob/master/CONTRIBUTING.md#how-to-increase-the-chance-of-being-accepted

[pzi]

Hey @hbjORbj , my bad. Copy/paste error. Fixed now and rebased on master.

[pzi]

Would be awesome to get this into the next release if possible please @hbjORbj

[pzi]

@eps1lon is it possible to get this reviewed, please? It's been sitting here ready to go for 12d :/

[pzi]

Can someone please review this? Apparently argos detected changes (that have nothing to do with the content of this PR)... This has been open for more than a month now...

Edit: Looks like argos is ok again. please review and merge if you agree with the proposed changes.

[pzi]

@mnajdova Would you mind reviewing this PR, please?

[pzi]

@siriwatknp would you mind reviewing this PR, please?

[siriwatknp]

@siriwatknp would you mind reviewing this PR, please?

Sure, I am reviewing it.

[siriwatknp]

👍 Thanks for the contribution and so sorry for the delay. It will be released next week!

[pzi]

👍 Thanks for the contribution and so sorry for the delay. It will be released next week!

Awesome, thanks for getting back to me @siriwatknp, looking forward to being able to use the StepperContext soon.

[Moshyfawn]

Hey, a great proposal, very convenient!

I'm tinkering with an idea of exposing the Stepper methods along the Stepper state.

IK MUI doesn't provide functions to update the activeStep out the box; something like goToNextStep. It leaves the implementation to the user, which pushes them to create an additional context to expose such methods.

const Funnel = () => (
  <Stepper activeStep={1}>
    <Step>
      <StepLabel>Label</StepLabel>
    </Step>
  </Stepper>
  <StepperMethodsProvider>
    <StepComponent />
  </StepperMethodsProvider>
)

const StepComponent = () => {
  const { goToNextPage } = useStepperMethods()
}

Is this the idiomatic way to deal with providing the custom Stepper methods by creating a custom StepperMethodsProvider or would it be a good idea to propose a unified Stepper interface to potentially expose them down the React tree?

[siriwatknp]

@Moshyfawn Thanks for the feedback. Can you open a new issue and provide a Code sandbox that replicates what you need?

If there are more people upvoting on the issues, we might work on it. Let's discuss first.

[Moshyfawn]

@Moshyfawn Thanks for the feedback. Can you open a new issue and provide a Code sandbox that replicates what you need?

If there are more people upvoting on the issues, we might work on it. Let's discuss first.

Got it! Thank you for your amazing work!

[pzi]

Thanks for the merge @michaldudak