[x] All keys within the values in the state are accessible in the schema (Ex: if you create a img_url key in the state, make sure your database also has a column that contains an img_url)
[x] Correctly formatted
[x] Sample state is rendered with 3 back ticks before and after. 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
img_urlkey in the state, make sure your database also has a column that contains animg_url)entitiessessionerrors(here or inui)ui(if needed)commentsinside ofposts