-
-
Notifications
You must be signed in to change notification settings - Fork 176
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
Issue with isValidated when used with Redux's @Connect #92
Comments
@narendravenkata Tnx for raising this. I haven't tried it with redux's @connect - I'm guessing it wraps StepZilla with a HOC and therefore the reference is lost. If this is the case, it's a issue we should try and fix as redux support is very important to StepZilla. @agent3bood @zeel @aapzu @elisechant @avivr have you guys seen this in your work on StepZilla, anyone can recommend a fix? Would appreciate heaps Thanks all... |
@narendravenkata @newbreedofgeek Looking forward for solutions In my project we got stuck with the same @connect Issue. using 4 steps loading dynamic components . Not triggering isValidated(). Somehow made it to work from child to parent using props, Whatever we do step at index 0 never triggers. Thanks |
Duplicate of #55 |
@narendravenkata @zeel I has the same issue, and I saw that a lot of other people have this kind of issue as well. I have seen several opened issues with the same topic without a proper solution. Is there some light at the end of the tunnel that we can hope for? Is there any hope that we can use redux and Stepzilla in the same project? This is a great library and thanks for all the work you invested in. |
Same issue with i18next package in next.js project. |
Is this issue has a solution or not yet? |
Hi I am using redux along with stepzilla, i need to save values at every step so I am using @connect with redux and isValidated() is not triggered , I tried to use @connect in Main component where we define steps and send required fields as props to each step but i am not able to get it done.
Please help me with this issue
The text was updated successfully, but these errors were encountered: