Great job! Look really good, just a few things. Let me know if you have
any questions about my comments for tags. remember that you must
finish the wiki before you start coding tomorrow.
MVP List
[x] Great! Could you add a timeline to your MVPs?
Wireframes & Component Hierarchy
[x] Wireframes look good!
[x] For the NotesContainer and NotebooksContainer, you will probably
also have a singular NotesContainer and NotebookContainer, so to
make it easier on yourself, I would suggest adding List or Index
into the name. So NotesIndexContainer and NotebooksIndexContainer.
State Shape
[x] Be careful nesting lists of ids inside of other slices of state, for
instance notebooksId: [1]. This means that if a user creates a new
notebook, you now have to update both the notebooks slice and the
users slice (to update the list of IDs).
Routes
[x] Looks great!
Schema
[x] Might want to include a user_id to the notes table
[x] For tags, you will want a tags table that will hold the names of
all of the tags, and then a taggings joins table to connect the tags
with the notes.
Design Docs Feedback
Great job! Look really good, just a few things. Let me know if you have any questions about my comments for tags. remember that you must finish the wiki before you start coding tomorrow.
MVP List
Wireframes & Component Hierarchy
NotesContainerandNotebooksContainer, you will probably also have a singularNotesContainerandNotebookContainer, so to make it easier on yourself, I would suggest addingListorIndexinto the name. SoNotesIndexContainerandNotebooksIndexContainer.State Shape
notebooksId: [1]. This means that if a user creates a new notebook, you now have to update both thenotebooksslice and theusersslice (to update the list of IDs).Routes
Schema
user_idto thenotestabletags, you will want atagstable that will hold the names of all of the tags, and then ataggingsjoins table to connect thetagswith thenotes.