Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Practice React ToDo List Code Review #3

Open
wants to merge 42 commits into
base: dev
Choose a base branch
from
Open

Conversation

amrendrakind
Copy link
Owner

  • Update Readme.md
  • Add Component lifecycles
  • Add Delete todo
  • Linter error fixed
  • Add Hamburger Menu
  • Add SinglePage.js
  • Update Navbar.js
  • Update Router set up
  • Add Router set up
  • Add About and No Match pages
  • Add key down events
  • Add input field editable
  • Linter Error fixed
  • Add styling
  • Add styling
  • Add TodoItem.module.css
  • Updated App.css
  • Updated App.css
  • Updated InputTodo
  • Add InputTodo completed
  • Add handel Submit functionality
  • Add InputTodo

@amrendrakind amrendrakind changed the title Practice React ToDo List Practice React ToDo List Code Review Jun 1, 2023
Copy link

@Ol-create Ol-create left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @amrendrakind 👋 ,

Good job so far working on the project requirements!

There are some issues that you still need to work on to go to the next project but you are almost there!

codeReview3

To Highlight 🎯

  • No linter errors. ✔️
  • GitHub flow is followed. ✔️
  • Good Pr title/description ✔️
  • Good commit history ✔️

Required Changes ♻️

Kindly fix the issues described in the pr thread below in order to get an approval

Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.

Cheers and Happy coding!clapclapclap

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me @Ol-create in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.
Happy coding! 🎉 🎉

src/App.test.js Outdated
import { render, screen } from '@testing-library/react';
import App from './App';

test('renders learn react link', () => {
Copy link

@Ol-create Ol-create Jun 1, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Please consider adding a description to the test: It's helpful to provide a description
    for the test case to make it more descriptive and easier to understand. 👍

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank buddy, I have change the test name to be more descriptive 👍

Comment on lines 10 to 18
style={{
fontSize: '6rem',
fontWeight: '600',
marginBottom: '2rem',
lineHeight: '1em',
color: '#ececec',
textTransform: 'lowercase',
textAlign: 'center',
}}
Copy link

@Ol-create Ol-create Jun 1, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • I suggest you use CSS classes instead of inline styles: For better separation of concerns,
    it's generally recommended to use CSS classes instead of inline styles.
  • You can define a CSS class for the header styles and apply it to the header element. 🎉 🎉

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have change a new file to style the Header.js
Thanks for bringing to my awareness the separation of concerns. 💯 ❤️

Copy link

@Ol-create Ol-create left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Status: Approved ✔️:confetti_ball:

Congratulations! 🎉 Project Approved ✅

Good job so far. Well Done.👍🏻
Your project is complete! There is nothing else to say other than... it's time to merge it :shipit:
codeReview4

To Highlight 🎉

  • No linter errors. ✔️
  • Git flow is followed. ✔️
  • You have followed JavaScript best practices. ✔️
  • Professional README file. ✔️
  • PR has a good title and summary. ✔️
  • Your app works as expected 💯 🥇
  • Your Design looks awesome, keep rocking 🚀

Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.

Cheers 🥂 and Happy coding!!! 👯💻

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please ping me @Ol-create when you comment so I can receive the notification.


As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

@amrendrakind
Copy link
Owner Author

Thank you my friend for all your time and effort. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants