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

React.JS Todo App with Drag and Drop

react, tailwind-css
UnsuspectedNoob•230
@UnsuspectedNoob
A solution to the Todo app 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?

I actually like the hover on the circle borders for the tasks. I did not know they could work like that. I'm most proud of the drag and drop, obviously. Dnd-Kit worked its magic, I could actually do it from scratch as well.

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

The theming was a slight issue, because I was hard-coding the tailwind classes. I overcame by abstracting the colors, and implementing them into the tailwind.config.js and index.css.

I also had problems with dnd-kit, it wasn't allowing the first inputted task to be draggable, but it fixed itself when I made the first index of the task start from 1 not 0.

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

When the tasks get to the amount which they exceed the height of the screen, how do I not make it not get a scroll bar horizontally ?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    markus•2,800
    @markuslewin
    Posted 11 months ago

    Hi!

    Remove the w-screen on the div that's a direct child to #root. It's a block element in a flow layout, so it'll grow to the edges of the screen either way. 100vw sets the element to be 100% of the viewport width, but it doesn't account for the size of the scrollbar. When the page starts scrolling, there isn't enough room for both the 100vw element and the scrollbar, and so the element starts overflowing.

    Marked as helpful
  • Chiemeka Okongwu•550
    @Chiemeka2006
    Posted 11 months ago

    this is a really good project, why dont you make sure to save the todo lists to local storage and also make the theme switcher to be saved to local storage, thats sure to bring more reality and life to your project. ill be uploading my own todo list u can check it out although i might not do the drag and drop, but i might try to find a ibrary out there that could help me accomplish that

    Marked as helpful
  • Chiemeka Okongwu•550
    @Chiemeka2006
    Posted 11 months ago

    also to your question "When the tasks get to the amount which they exceed the height of the screen, how do I not make it not get a scroll bar horizontally ?" you can set the parent of the lists to have the property of overflow-y: auto; and also give the parent a max-height property, how i decided the value i was gonna put for this property was by using the inspector tool to view the height of 1 list then multiply by 6. in your case the height of 1 list is 56px so u should set max-height to 336px; . Then how to get rid of the scrollbar that will appear in the parent container due to the overflow-y: auto; lets say ur parent element is a ul you do : ul::-webkit-scrollbar { display: none; scrollbar-width: 0rem; }

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

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