# Sample State

[andy-h-2016]

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

[andy-h-2016]

• You might not need tags in your posts slice of state. However, if you do, you should store an array of tag id's. An array of tag id's would be easier to iterate through to create your links, and there would be less duplication of data.
• email_verified and profile_links should be bonus; they do not add much visual value from a recruiter's standpoint. Focus on the tougher and more valuable portions of your project such as your posts CRUD and creating your pages.
• Missing session and errors slice of state
• Are you planning on using ui slice of state?

[andy-h-2016]

Please make the change we discussed to the tags field nested inside of your posts slice of state.