# Sample State:

[TahjDev]

• [ ] 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
    • [ ] entities
    • [x] session
    • [x] errors (here or in ui)
    • [x] ui (if needed)
  • [ ] Should NOT have nested slices, aka comments inside of posts
    • Some info from other tables is ok, for instance:
      • the author username and im'geurl 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

[TahjDev]

• So ratings should not be nested underneath products. They should have their own slice of state like the rest of the tables. You can have an array of id's inside of products to reference them.
• Categories should also have their own slice of state and you can just use the category_id on the products table to reference them
• Also the formatting is a bit off in terms of the extra tabbing from one key value pair to the other could you fix that please
• The key should be entities not entity
• Do you not want the birthday in the users slice of state?
• IN your sample state product has a name key when in the schema its's title
• I see quantity in your product in sample state but not in the product table in your schema
• I'm confused about the shopping_cart sample state, why is there a nested key of cart, you can just the instances nested under keys inside shopping_cart and have an array of products that is in a single order? as well as the buyer
• You won't be saving the session token in state underneath session just the user's id so you can access the user's information from the databse