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

Shopping Cart React Component

react
Jon D•190
@jcad57
A solution to the Product list with cart 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'm super proud that I am even completing this challenge. While it's not perfect, I realize there are a few techniques I probably still need to learn to have created this more efficiently. This was my first attempt at a React project after taking some courses. Next time I will plan out the project better. I was eager to get started and did not really plan out how props will flow through the app very well.

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

I ran into an issue with updating the quantity in the cart array. I could not figure out for the longest time how to update it without adding a item to the array. I spent a lot of time googling and also took a step away from the project for a bit. When I came back I was able to solve the issue pretty quick ha. The other challenge I ran in to and did not solve is managing SVG's as well as changing them dynamically as per the design spec wants. When you hover over the 'increase or decrease quantity' (+, -) buttons they are supposed to change fill colors but I was unable to get that to work. SVGs are a weak area for me for sure.

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

I could not find a good way to create the page-dimming effect when the confirmation modal pops up. I ended up using a box shadow and I mean it sort of worked but it was not part of the design file.

I would love any feedback at all on the "cleanliness" of my components, logic and JSX since this was my first time attempting a react app.

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 Jon D'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.