Issue #3 - Sample State

[keginzburg]

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

Comments

1. What is the purpose of your categories slice of state? It's somewhat unconventional and I'm curious as to why we need it.

[cgreen66]

Maybe it will be too time consuming and not needed for this project

I was only considering a separate categories slice for a couple reasons:

• Making it simpler to render category lists in the UI (like dropdowns or sidebars) without needing to extract them from all products each time.
• If I need to update category names or add new attributes to categories, it's much easier to manage this in a dedicated slice rather than updating every product entry.

But given that it probably will take more time and add some complexity maybe best to just not do that for now