FSP Sample State

[mwmadsen67]

Sample State

• [x] State shape is flat!
• [x] State's keys are camelCased
• [x] All keys within the values in the state are accessible in the schema
• [x] Correctly formatted
  • [x] Sample state is rendered with triple backticks, and the language ```javascript...```). This will display the state as a code block instead of a giant line of text
  • [x] Top level slices
    • [x] entities
    • [x] session
    • [x] errors (here or in ui)
    • [x] ui (if needed)
  • [x] Should NOT have nested slices, aka comments inside of posts
    • Some info from other tables is ok, for instance:
    • the author username and imageurl for a post. basically any info that the user can't change
    • like count and a boolean on whether the user likes the post instead of a likes slice

[mwmadsen67]

Hi Brendan, everything looks good. Only thing I would add is that in the products slice of state, it should have an imageUrl. Its not something you'll store in the database, but you'll use active storage and aws, as you'll find out with some of the later readings, and you'll have access to it in the global state.

Otherwise it looks great!

[btsuda11]

Thanks Mike! I was wondering if it is necessary for the cart_items to have price as well so that the cart can be updated or is it sufficient for only the products to have price?

[mwmadsen67]

you could decide to store the total price on the cart state if you'd like, up to you! It's really just a choice between doing the math on the backend and sending it up, vs doing the math on the frontend.