Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Todo app

Adarsh Rai•560
@AdarshRai0
A solution to the Todo app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


👾 Hello, Frontend Mentor coding community. This is my solution for the Todo app.

Feel free to leave any feedback and help me improve my solution or make the code clean!✨❤️

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adarsh Rai•560
    @AdarshRai0
    Posted almost 3 years ago

    Thankz for such an Explantion..!!!✨ Surely Implimenting this Thought in code..

  • Radh Akhmad•60
    @fadhilradh
    Posted almost 3 years ago

    Hi Adarsh,

    Your app looks amazing, without bugs and has great animations, well done !

    I have one feedback for you when I forked your project and looked at your script.js file. It is quite long and not very readable, especially the main function. What you can do is you can extract some code inside your function to another smaller function. Example : Instead of :

    function main() {
       code...
       code.. 
       code..
    }
    

    You can write as :

    function main() {
       function1()
       function2()
       function3()
    }
    

    This is more readable for the one who will read your code (your co-workers) and cleaner as it follow the principle of one function should only do one thing and one thing only. Also, make sure your function name is meaningful so others can understand its job in one glance.

    Secondly, you can further improve your code by separating your code into several files, grouping similar functions and variables inside a file and making use of import and export statements.

    For example you can split into three files : script.js for storing your global variables and main function, addTodo.js for adding todo and utils.js for other functions. Then, you can export function to be available in another file. For example :

    Firstly, you need to make change to your HTML file, add type="module" to your link to script.js file. This will make your JS files able to import and export function and variables to each other.

    For example :

    // addTodo.js
    export function addTodo() {
      …doAwesomeThings()
    }
    
    // main.js
    import { addTodo} from “./addTodo.js”
    
    function main() {
    ...code...
    addTodo()
    ...code...
    }
    

    You can do this for every other function and group similar functions in one js file.

    Just reply me if something is not working.

    Hope it helps and good luck Adarsh!

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.

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