Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 2 months ago

Conference ticket generator using React.js

react, react-hook-form, tailwind-css, typescript, vite
Fanuel Amare•200
@Fanu-Cd
A solution to the Conference ticket generator challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

What I'm Most Proud Of:

I’m most proud of how I was able to successfully integrate React Hook Form, Yup, and TypeScript to build a clean, type-safe form validation system. Using React Hook Form made form management much easier and more efficient, reducing the amount of boilerplate code while still ensuring a smooth user experience. Additionally, Yup validation allowed me to enforce strict validation rules while ensuring that the form was highly responsive. By combining all of these tools, I was able to create a maintainable and scalable solution for handling form inputs.

Another thing I’m proud of is the type safety I achieved by using TypeScript. By defining types for forms, validation schemas, and form states, I minimized the risk of runtime errors and made the development process smoother.

What I Would Do Differently Next Time:

Next time, I would likely invest more time in optimizing performance, especially for larger forms. For example, I could explore ways to better manage field arrays in React Hook Form to handle dynamic form fields more efficiently.

Additionally, I would like to improve accessibility further by ensuring all form elements are properly labeled and the form is fully accessible with keyboard navigation. While I’ve made an effort to follow best practices, I believe there’s always room to improve accessibility, and I’ll focus more on that in future projects.

What challenges did you encounter, and how did you overcome them?

Challenges I Encountered:

During this project, I didn't face any major challenges, but it was a valuable learning experience as I was able to apply various technologies like React.js, TypeScript, React Hook Form, Yup, and @hookform/resolvers to build the application.

How I Overcame the Lack of Challenges:

I believe the success of this project came from careful planning, thorough research, and taking time to understand the tools I was using. I had worked with similar libraries before, so the integration of React Hook Form with Yup for form validation and TypeScript went smoothly. By referring to documentation and checking examples, I was able to implement everything efficiently and without significant roadblocks.

While it wasn't necessarily challenging, I did make sure to focus on clean code, optimizing the form handling and validation, and creating a user-friendly interface. The ability to work smoothly through the development process and ensure all parts came together as planned was very rewarding.

What specific areas of your project would you like help with?

At the moment, I don't need any assistance, as the project has been completed successfully. However, I always welcome feedback on areas such as code optimization, user experience improvements, and best practices for working with React, TypeScript, and form validation libraries like React Hook Form and Yup. I'm constantly looking to improve and refine my skills, so any insights on how I could enhance my approach or the overall performance of the app would be greatly appreciated.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Fanuel Amare's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.