Giter VIP home page Giter VIP logo

Comments (4)

newbreedofgeek avatar newbreedofgeek commented on June 10, 2024

@stanleycyang I've confirmed that this works fine in 4.4.4

Update the example code as below and it starts at Step 3.

render() {
    const steps =
    [
      {name: 'Step1', component: <Step1 getStore={() => (this.getStore())} updateStore={(u) => {this.updateStore(u)}} />},
      {name: 'Step2', component: <Step2 getStore={() => (this.getStore())} updateStore={(u) => {this.updateStore(u)}} />},
      {name: 'Step3', component: <Step3 getStore={() => (this.getStore())} updateStore={(u) => {this.updateStore(u)}} />},
      {name: 'step4', component: <Step4 getStore={() => (this.getStore())} updateStore={(u) => {this.updateStore(u)}} />},
      {name: 'Step5', component: <Step5 getStore={() => (this.getStore())} updateStore={(u) => {this.updateStore(u)}} />},
      {name: 'Step6', component: <Step6 getStore={() => (this.getStore())} updateStore={(u) => {this.updateStore(u)}} />}
    ]

    return (
      <div className='example'>
        <div className='step-progress'>
          <StepZilla
            steps={steps}
            preventEnterSubmission={true}
            nextTextOnFinalActionStep={"Save"}
            hocValidationAppliedTo={[3]}
            startAtStep={2}
           />
        </div>
      </div>
    )
  }

from react-stepzilla.

newbreedofgeek avatar newbreedofgeek commented on June 10, 2024

Closing as no feedback was received on advice given. Please raise issue again with more details if needed @stanleycyang

from react-stepzilla.

ajendrex avatar ajendrex commented on June 10, 2024

Hello, I got into this problem because startAtStep value changed after StepZilla's constructor ran. I was able to manage it by using startAtStep={startStep} key={startStep} props. Please let me know if you think this solution is fine or if you have a better idea...

Thanks for your work!

from react-stepzilla.

rasfdeveloper avatar rasfdeveloper commented on June 10, 2024

Hello, I got into this problem because startAtStep value changed after StepZilla's constructor ran. I was able to manage it by using startAtStep={startStep} key={startStep} props. Please let me know if you think this solution is fine or if you have a better idea...

Thanks for your work!

Can you be more specific about how you solved this problem?

from react-stepzilla.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.