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

Product cart list component

react, tailwind-css, vite, typescript
Utkarsh9571•640
@Utkarsh9571
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?

Well this project has a lot of part to be work on, it was a junior level challenge, but it did looks like that, i completed with help of Gemini in rendering the selected products with correct quantity.

and now i know how to lay the data from json, update states, create counter like this one has and some level of conditional rendering.

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

i started it in typescript, so when gemini provide the solution for rendering selected cards in the cart, i was getting a error which took a lot of time, it made me convert the files in (jsx) from (tsx) and still was not working,

but later got a solution and i still had to convert them into (jsx) but i think it is fine.

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

look at the code, one function in App component, it was doing everything, its also updating the counter,

if you look at my functions to update the counter, they look a little different,

its gemini's code, its saying that when you click of increase button, it tell the App (hey, app update the quantity by 1), believe me gemini says exactly like that, and (i'm like what the ...??) tell me how it works, and it keeps saying that it does work like that,

i think it become some kind of automatic function which works under the hood, can anyone explain me how it works or where i can find my answers.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • legaz•550
    @Legaz-le
    Posted 2 months ago

    Good job but you need to fix your cart it shoudn't take whole height. I would recommend you to separated the items and cart in different files and in one file just make flex and flex-col for small devices. Also another thins your items should take col-3 in width:1024px but yours take col-2 but generally it okay but need to work on layout and responsiveness for devices.

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