resolves #22 terrible string building, but it works for now.
Is grabbing Location record in the tweet builder the correct way to do this? Could pull out into a separate function for testing purposes? I suppose if the appt. is committed to the DB it has to have a valid location id?
resolves #22 terrible string building, but it works for now.
Is grabbing Location record in the tweet builder the correct way to do this? Could pull out into a separate function for testing purposes? I suppose if the appt. is committed to the DB it has to have a valid location id?