Skip to content

Design Docs Review #1 #1

@jliversi

Description

@jliversi

Hey Jon, great work on your design docs so far! Below are my comments:

MVP LIST
Rich-text editing:

  • What exactly is included in a “clean user interface”? Be specific for future reference

SCHEMA
Notes:

  • You’ll want to make the content column have a type of “text” (string maxes out at 256 characters)

Tags:

  • Do you need to store the user_id on each tag? If you have a strong motivation, that’s fine, but I can’t think of a reason that that column would be necessary.

Taggings:

  • You don’t need a name column in your tagging table as this will be stored on the tags table, in whichever row is referenced by the tag_id

SAMPLE STATE

  • Each note should have an array of tagIds
  • Each notebook should have an array of noteIds

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions