Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Todo App (React, Styled components, TypeScript)

react, styled-components, typescript, framer-motion
Lee•170
@tripkmin
A solution to the Todo app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


🔗 Links

  • Github URL: Click here
  • Live Site URL: Click here

🛠️ Technologies Used

  • React JS
  • TypeScript
  • Styled-Components
  • HTML5, CSS
  • Framer Motion

🗒️ Core Features

  • Adding new to-do items
  • Toggling completion status of existing to-dos
  • Filtering to-dos
  • Theme switching
  • Drag and drop functionality
  • Responsive web design

⚡ Additional Features

  • When deleting a to-do, a toast is displayed with an "undo" option
    • If multiple items are deleted simultaneously with "Clear Complete," undoing will restore multiple items simultaneously
    • Undo is possible for previously deleted items while the toast timer is active
  • Variable textarea style
    • Expands dynamically up to 4 lines, then becomes fixed at 4 lines and includes a custom scrollbar
  • Keyboard considerations
    • Pressing Esc while editing a to-do exits the editing mode
    • Pressing Enter when adding a to-do immediately submits it
    • Pressing Shift + Enter when adding a to-do creates a line break
    • All elements can be accessed via the tab key
  • Smooth theme switching
    • Transition of the background with a gradient does not work, so opacity transition of pseudo-elements is used to resolve it
    • The header image is handled in the same way

🚧 To-Do Features to Improve

  • Issue with touch drag-and-drop not working on mobile devices.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Lee'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.