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

React Context API - For global state management of cart data

react, tailwind-css
OlgaMinaieva•80
@OlgaMinaievaWebDev
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?

How to implement modals with React portals for better UI layering

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

How to manage state globally using React Context for cart items and quantities

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Antoine•330
    @super7ramp
    Posted about 2 months ago

    Nice work 🙂

    I find your approach with React Context interesting. It could be really useful for large projects with lots of components and shared states. Thanks for sharing this!

    I learned the existence of React Portals thanks to you 🙂 As an alternative, you may consider using the native <dialog> element with a useRef to manage the modal:

    import {useRef} from "react";
    
    function App() {
        const modalRef = useRef(null)
        const showModal = () => modalRef.current?.showModal()
        const closeModal = () => modalRef.current?.close()
        return (
            <>
                <button onClick={showModal}>Show modal</button>
                <dialog ref={modalRef}>
                    <h2>Hey!</h2>
                    <button onClick={closeModal}>Close modal</button>
                </dialog>
            </>
        )
    }
    
    export default App
    

    Concerning the logic, implementation works as expected, expect for one bug: Items in the confirmation order modal are removable, whereas they should not. Once it's ordered, it's ordered 😉 It leads to a confusing behavior:

    1. Add an item to the cart → item is added to the cart
    2. Confirm order → confirmation modal appears
    3. Remove the item from the cart → the modal disappears 🤔
    4. Add any item to the cart → the modal reappears with the new item, without clicking on the confirm order button 😮

    Concerning the appearance, I find your approach interesting again, code is really compact with Tailwind!

    There are some details that could be improved though:

    • Dessert in the grid should have a solid outline when added to the cart
    • There are differences in colors and button sizes compared with the design.
    • The '-' and '+' buttons are not exactly centered in their circles
    • Buttons are missing hover effects
    • Modal is missing an open/close animation

    Overall, kudos for your work and thank you again for sharing it 🙂

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

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