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

Todo App React

tbrownlee•350
@tbrownlee
A solution to the Todo app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


How can I make the checkboxes like the ones in the design file?

How do I save info in React on refresh?

How do I implement drag and drop?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Igo Brasil Monteiro•150
    @igomonteiro
    Posted over 2 years ago

    Hi tbrownlee, you did a nice job!

    About your questions:

    How can I make the checkboxes like the ones in the design file?

    • To do that, you need to "hide" the standard html checkbox input and wrap the input inside a container, then style the container as you want. The checkbox component that you will create can be either a controlled or uncontrolled component, you choose. To set the gradient inside the checkbox, you need to use the property background-image, not the background-color, take a look at my solution. Also, check out this article: Custom checkbox component in React or this one (but this one is in Portuguese) Checkbox component in react

    How do I save info in React on refresh?

    • To save the todo info without implement any API, you can use the browser local storage. You can save the todos in the localStorage everytime the user create or update (checking/unchecking) a todo, in resume, implement this logic using the useEffect hook. In addition, you can create a custom hook (that implement the logic of saving/getting from localStorage) and also use the ContextAPI to manage the todo states. To read more about how to use the localStorage, see this article: Todo app using localStorage and react hooks

    How do I implement drag and drop?

    • To do that you can implement your own drag and drop functionality, but this will be kinda hard, or you can use some drag and drop library. I recommend dnd kit or react beautiful dnd - i'm not a big fan of this last one because the bundle size is huge XD but i've used it in my solution. In this two libs, you will need to implement a function to handle the onDragEnd event. In this function, you will set your new states reordering the element in the array using the index returned by the onDragEnd event of the dragged element. To reorder the array, you can use the splice method, check the docs here.

    IMPORTANT NOTE: splice is a destructive method, which means it modifies the array on which it is called, don't use it in directly on your react state, instead create a new const that store the current todo states and then use the splice method on it, then set your todos state with the new elements by using the setter of your useState.

    One more observation: about your mobile design, reduce the breakpoint to 375px, in your solution the background-image is switching to the mobile image too soon, this way, the image is getting the sides "cut off".

    Good luck if you implement these improvements, but your solution turned out pretty cool.

    Hope you understand, english is not my native language, but i'm trying.

    Keep up the hard work! 🚀

    Marked as helpful

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

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.

Oops! 😬

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

Log in with GitHub