Sample State

[KevinHJo]

• [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

• Use associations and joins tables in the database schema over saving arrays of id's in the state
• simplify your database schema, then revisit using separate slices for messages, reactions, etc. instead of arrays of ids

[emilylichtenberg]

I'm a little confused when to use an array of IDs then. I thought it was for one to many relationships and the many to many used associations and joins tables.

[KevinHJo]

I talked to the other instructors, and it seems to be fine to have the arrays. I was going off of what I was told during my own fsp, but maybe things have changed. You can use an array of ids when needed

[emilylichtenberg]

If I can get all the needed information through associations and joins I can remove and have less data stored in state.