doctor can invite an existing patient whom can then signin and have the association to the doctor made
If a guest enters in an old invite where the association has already been made then the user is redirected to the root path to login, added this conditional logic to the invites controller, very very very messy and ugly with duplication, will need to refactor and push logic down to the model layer
feature spec'd a patient inviting a doctor, and their acceptance in cases where they are/are not members of Tredule
prepped the password reset flow for patient, now implement the record update - unsure of need for a security question if there is a password reset auth token
added specs for the password reset path, yet to figure out the time testing, might need time cop, horrible horrible horrible user queries in the password resets controller, uuuuuuuuuugh, need a better query methodology, fucked user model
password reset token model specs
refactored the Invites controller and pushed all the logic down into the Invite model, now cleaner and reads better
Merge pull request #5 from phoenixbox/invite-poly

Invite poly