[ ] All keys within the values in the state are accessible in the schema
[ ] Correctly formatted
[ ] 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
[ ] Top level slices
[ ] entities
[ ] session
[ ] 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
Hey Jacob! Be sure to revisit the examples in the full stack section of app academy open! Users, products, carts, listings, reviews and anything else that could be in your schema should be under entities.
Sample State
```javascript...```
). This will display the state as a code block instead of a giant line of textentities
session
errors
(here or inui
)ui
(if needed)comments
inside ofposts