- more tests. would have separated out and added tests for updateCart at the very least
- wouldn't have used a switch statement in ProductPage, I know there's a cleaner way to adjust the types to handle this but I couldn't figure it out quickly enough so decided to move on
- would have used redux instead for the cart state, to avoid passing the setter down the tree
- would have added the facility to handle different currencies when formatting prices
- would have handled multiples of the same item to make cart view cleaner
- would have curried updateCart or similar to avoid replicating the onClick code in each product
You should be able to run the following commands to get started:
nvm use
yarn
yarn start
data - Some mock data for products
features - Probably the most important directory as it is where all the functionality is implemnented
layout - This directory can be completely ignored for the purposes of the test
services - Contains a mock api client
types - Common TypeScript definitions for some of the objects we use throughout the codebase
The tasks have been ordered in terms of easiest to hardest. You don't need to complete them all and feel free to say things like "If I had more time, then I'd do it this way"
By default, the prices are showing as e.g. £6, in the real world this price would typically show as £6.00
Write some code to show prices as £6.00 wherever they're rendered on the site.
If you look in the data directory, we can see that there is a Pizza product available, but it isn't rendering. The second task is to get the Pizza rendering, including showing the extra information on the Pizza object
Add a product to basket, feel free to do this any way you like, such as:
- Callbacks
- HOCs
- Redux
- context API