product-list-with-cart app demo using (react redux js css)
Design comparison
Solution retrospective
I developed a product list with a cart feature using React and Redux. The application allows users to browse products, add them to their cart, and view the cart with a detailed breakdown of items and their quantities. The project also includes functionality for calculating the total cart value based on the selected items. a model to be previewed on submitting the order, then starting a new order.
What challenges did you encounter, and how did you overcome them?I enhanced my skills in Redux state management by using objects over arrays for better performance and easier access to items by key. I also learned the importance of structuring my Redux state to handle complex features like the cart, where I used the product name as the key. Additionally, I focused on creating reusable and maintainable components, like CartProductDetail, to organize the codebase better. I also got to dive deeper into using CSS for styling and maintaining clean, readable code throughout the project.
What specific areas of your project would you like help with?I need support in reviewing my code to ensure it aligns with clean code principles. I'm particularly interested in feedback on the readability, simplicity, and maintainability of my code. I would appreciate a detailed review to identify any areas where I could improve my coding practices, such as naming conventions, code structure, and the use of functions.
Community feedback
- @TedJenklerPosted 3 months ago
Hi @MarwanElZaher,
Nice project! It’s fully responsive, so great job on that.
I noticed you’re using Create React App, which some people consider less optimal for bundling React projects. You might want to explore Vite or other modern tools to enhance your setup.
For better organization, I’d suggest placing Redux components in separate folders. For example, put your store configuration in app/store.js and slice logic in features/state/stateSlice.js, or features/newLogic/newLogicSlice.js if more logic is added in the future. Typically, for larger projects, components are organized into one folder, with separate folders for pages and modules. Avoid deeply nesting everything in one folder.
Consider naming and placing files like constants.js and data.js in the root directory. This can help reduce unnecessary nesting and make your project easier to navigate, especially as it grows.
Overall, your project works well, and I didn’t find any bugs during my scan in DevTools.
I hope this feedback is helpful!
Best, Teodor
0
Please log in to post a comment
Log in with GitHub
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