JQQ, this might be the most helpful video I have watched from you. Love the longer content. You could make a full series off this. Thanks for being awesome and sharing so much all the time!
Hey JQQ, the side navigation is very interesting, could you go through creating Side Navigation from Scratch for sure I am interested in that, to see how you would approach it, and possibly.. an interesting twist, what about including sub steps or nested steps .. how you approach dealing with nested steps and the highlighting ?
Do you think its necessary to have a route based stepper, I would do a client component stepper, where we would have the same logic, i dont see why we need more routes like add/step-one. Having a route doesn't bring benefits unless we want to send someone directly to step-n(2,3,4 whatever)
I don't think it's necessary. In some ways, it makes things a bit harder, but in others, it simplifies things because there is less we have to track in state I think. I definitely wanted the user to be able to refresh the page on a given step and not go back to the beginning. You could also do that with query params. For example "/add?step=one" or something like that. What do you think would be the greatest benefit of doing it all client side?
your use the link right if i didn't submit the step form so can i change the link to step 3 in url it will open that form so ,react-hook-form has trigger function for this without using links we can use switch case or condition and return
Nice content. But still there are separate backend and developer do integrate api in NextJS app. Can you please make a video how to integrate APIs in NextJS 14/15 app
JQQ, this might be the most helpful video I have watched from you. Love the longer content. You could make a full series off this.
Thanks for being awesome and sharing so much all the time!
recaptcha would be nice. Do you deal with spam/crawlers?
Yay! So glad to hear that. I think I'm going to do more of these longer ones!!
Ooh that's a good idea! I'll add that to the backlog :)
User should only be able to move next after the step is validation so there's no need to go back due to error. Simple and straightforward.
Great video! Thanks for sharing your process.
So glad you enjoyed it!
This!!! More of this!!! 🔥🙌🏼
Hey JQQ, the side navigation is very interesting, could you go through creating Side Navigation from Scratch for sure I am interested in that, to see how you would approach it, and possibly.. an interesting twist, what about including sub steps or nested steps .. how you approach dealing with nested steps and the highlighting ?
Great course, and also to achieve same aim material ui stepper does this in seconds
How can we handle conditional field validations inside multistep forms in Zod since schema.shape misses out on the optional fields and objects.
Do you think its necessary to have a route based stepper, I would do a client component stepper, where we would have the same logic, i dont see why we need more routes like add/step-one. Having a route doesn't bring benefits unless we want to send someone directly to step-n(2,3,4 whatever)
I don't think it's necessary. In some ways, it makes things a bit harder, but in others, it simplifies things because there is less we have to track in state I think. I definitely wanted the user to be able to refresh the page on a given step and not go back to the beginning. You could also do that with query params. For example "/add?step=one" or something like that.
What do you think would be the greatest benefit of doing it all client side?
your use the link right if i didn't submit the step form so can i change the link to step 3 in url it will open that form so ,react-hook-form has trigger function for this without using links we can use switch case or condition and return
Can be done in more better way using zustand and validating form at the time.
Never heard of zustand. What is that and why do you love it?
Bro @@JamesQQuick, zustand is a state management library alternative to redux.
Compared to redux it's very simple and easy to work.
@@JamesQQuick state management library
Zustand is amazing
Great points there. This implementation was unnecessarily complicated
Nice content. But still there are separate backend and developer do integrate api in NextJS app.
Can you please make a video how to integrate APIs in NextJS 14/15 app
I would like to see how you do it
It's good tutorial and helpful but your way in clarify code need more simplify to be not complicated ❤❤❤
Multi page forms that are not spa are simply done by persistenting in database
yep but it becomes costly for db hosting when every user rewrite data 1-3 time
@@funfstuck naa, that's nothing compared to data fetching traffic. This is a non-issue considering the time it takes to fill each form.
Tks for tutorial, autosubscribe
Please make additional tutorial like the result is becoming pdf
its got better if we stored on url schema 🎉
Not sure what you mean there? Can you clarify?
@@JamesQQuick i mean use store using url params instead localstorage
@@JamesQQuick i mean stored data on url search params, instead localstorage
@@ilmanmanarulqori5632 including files?
@@aberbaCodes not possible