1:05:20 No errors till now going smooth

1:23:23 Going on

You are right, I might be wrong, but please correct it, adding onclicik listener on parent is always a better idea.

Thanks for the feedback, it motivates me to create more content.

I would be happy to help you, Can you please share your code base (Github link)

@@imranshaikh0404 thank you for your response issues has been resolved ☺☺

@@vision9338 Have you deployed the project?

Thanks for the feedback, I'll try to make more.

I appreciate that you liked it, Please share this video in your friend circle if possible.

Hey Bhai, Thank you so much for your kind words! I'm really glad to hear that you're feeling positive about it all. May you be blessed with even more wisdom and success on your journey ahead. Always here if you need anything! 😊

1. Good question! Technically, we can store the image as a BLOB in the database, but doing so comes with additional maintenance overhead. Managing BLOB data in a database can lead to performance issues, especially as the size of the images grows. It can also make backup and recovery processes more complex. 2. I’m explaining this to you to give you an idea of how things work in real-world projects. In production environments, best practices are followed to ensure efficiency, scalability, and reliability. 3. It's not recommended to store BLOB data directly on your server for several reasons. For instance, if the database experiences a failure, you might lose all the image data. Managed services like Amazon S3, Cloudinary, or other cloud-based storage solutions are preferred because they offer redundancy, automatic backups, and scalable solutions. These services also have multiple replicas, ensuring your data is safe even in case of a server failure.

Hey , You make a valid point. For a step form, as more fields are added at each step, the complexity can indeed grow. However, the approach I shared was primarily intended to demonstrate a simplified solution, especially from an interview perspective. In real-world scenarios, we’d consider more scalable and maintainable approaches, like dynamic form handling or modular components, to manage complexity as the form expands. The goal here is to focus on the basic idea, but you're absolutely right to think ahead about how complexity can increase in such use cases.

Thanks for your support

Already done, Can you please refer this video kzbin.info/www/bejne/p4XWpGVqp9-VmdU

Thanks for the sub!, Noted your feedback

I got same error when I deploy app on vercel .but not get any solution

Glad you liked it

Glad that you found this series valuable, thanks for the compliment

Thanks glad you liked it

Thanks Already uploaded

You are so welcome!

Thanks for the sub!

You are most welcome

Good to hear this.

Nice, Sure you can definitely add your project whether it's frontend or full stack. it's good to have always projects in the resume.

Glad you think so!

Thanks for the visit

Hey, I will try to complete it in 35 to 40 days

Glad you liked it

Glad you liked it