Skip to content

craftedsro/notine

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Getting Started with Create React App

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Todo:

  1. Refactor code to production-grade quality.
  2. Find and describe bugs and issues.
  • App.tsx

  • infinite loop - todos are generated every 100ms React.useEffect asynchronously change state what force to re-render.

  • Todo.tsx

  • Force re-render of page - handleOnClick changes windows location what force page to reload that is unnecessary

  1. Add styling by your choice. (You can add styling library)
  • And.design was used.
  1. Demonstrate connection to backend API.
  1. Add Todo detail page (add routing to app, use context api for state management from fetch todos to render todos and detail)
  2. Todo component has defined shouldComponentUpdate lifecycle, but it can be done better, adjust it
  3. Optional: rewrite Todo component to FC (choose if you want, prepare explanation)
  • React.memo() When deciding to update DOM, React first renders your component, then compares the result with the previous render. If the render results are different, React updates the DOM. Current vs previous render results comparison is fast. But you can speed up the process under some circumstances. When a component is wrapped in React.memo(), React renders the component and memoizes the result. Before the next render, if the new props are the same, React reuses the memoized result skipping the next rendering.

About

Notine Homework

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published