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)
    • [ ] 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 Jason, it looks like most of the info in your sample state is just ids. You should be listing all information that you would potentially need for rendering content on your page. So pretty much every column from your backend except for protected info like passwords and session tokens.

Additionally, restaurants will need references to image urls, so that is another thing you would add. Even though image urls aren't saved in the database, they will be able to be accessed using active storage and aws, which you'll read about later.

[jason330]

Hi Mike! Sorry I initially thought the purpose of the sample state document was to get an idea of the structure and nesting rather than actual content/keys. Took another shot with your feedback, thanks!!

[mwmadsen67]

Awesome. Looks good!