Sample State

[x] State shape is flat!
[ ] State's keys are camelCased
- Make sure to go back through and correct this
[ ] 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)
- Make sure to add img_url if you decide to add it to your schema
[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
  - Make sure to add the JS (as I mention in the comments) before I can check this off
- [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:

Make sure to structure your code like this (the JS is super important because it will color code everything):
```
```JS
Code goes here
```
Ids will always start at 1, you should update your photo slice.
Users don't have bodies
Slice names should be plural because there can be multiple things in them
Tags and albums needs to be indented to the left, it looks like they are comments
has_many associations should store an array of ids:
- Albums slice should store an array of photoIds
- Photos slice should store an array of commentIds and tagIds
- Users slice should store an array of photoIds