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

Product List with cart in React

react
P
conormcfarlane•220
@conormcfarlane
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 would defiantly plan out my project more next time and think twice about where state management of certain components should live.

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

I had originally tried managing the carts state in the cart component. I had forgotten i would have needed to access the carts quantity state from the add to cart buttons in the dessert cards. Once i realized this i moved all cart state to App.jsx, which is where i should have put it in the first place.

The add to cart button also caused me more trouble when i was using conditional rendering on the button tag itself as i was trying to render the plus and minus buttons inside the original button tag, not realising this wouldn't work as i cant nest buttons inside buttons. Instead i made the increase and decrease buttons spans with onClick events.

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

Would like help with fixing the no scroll behavior for when the Modal appears. I wanted it to be the same as the mobile design in that when the Modal pops up, it brings the user to the top of the page where the H1 title DESSERTS is visible in the background while displaying the Modal, but when i enabled any type of no scroll to stop background scrolling, it also restricted me to actually being able to bring the user to the top of the screen for when the Modal appears

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dusvy_M•520
    @dovelm
    Posted 3 months ago

    I really liked your work

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