You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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
Looks solid! My only concern is that you should not reveal your users' session_token or password_digest within your frontend state. Nix those please, then feel free to close this issue.
The text was updated successfully, but these errors were encountered:
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
Comments
session_token
orpassword_digest
within your frontend state. Nix those please, then feel free to close this issue.The text was updated successfully, but these errors were encountered: