My templates

[haydenrou]

• Associate templates to a user on "use" and show their templates on a "my templates" page
• See router/routes.go TODO
• For this we'll need to add an id to users.

Note from a previous PR:

I'm undecided on the data-structure we want to go with yet. We obviously don't want a template to belong to one person via their username. At the least, it would be an ID.

Saying that, I don't know if we want to do some sort of joins-table-esque type deal between users and templates, or if we just straight up want to duplicate the template per use.

Considerations:

• A user may partially fill out a template and won't want it to completely change if the author made amends to it half way through completing it
• A user may want to use the updated version of the template next time they fill it out. Should they perhaps have an option to be able to use the same as last time, too? Maybe take this even a step further and you cannot update templates after creating them, but you can duplicate them? This could solve some problems.
• A user may want to amend the template themselves (is this functionality we even want to offer?)

[haydenrou]

In progress...

classDiagram
    class users {
        _id: ObjectId
        password: string
        email: string
    }
    
    class Question {
        _id: ObjectId
        title: string
        description?: string
        type: QuestionType
        options?: string[]
        min?: int
        max?: int
        order: int
    }

    class Template {
        _id: ObjectId
        title: string
        description: string
        created_at: DateTime
        default?: boolean
        questions?: Question[]
        user_id?: ObjectId
    }

    class Answer {
        _id: ObjectId
        question_id: ObjectId
        answer: string
    }

    users "1" -- "N" Template : "owns"
    Template "1" -- "N" Question : "contains"
    Question "1" -- "N" Answer : "has"

Loading

[haydenrou]

I'm of the thought that with the new structure / features we'll be building out for the MVP, this will come for free. We will decide on the data-structure as we go, and potentially use this as a base, but in general, I don't think this story will be needed after we have a dashboard. Or if it is, it'll be a single page to show history or something.