nplutt / vaccine-availability-notifications Goto Github PK

In order to allow others to develop the backend of for this project there needs to be a test harness that integrates with a local DynamoDB Docker container.

Ability to send an email to manage your preferences from the website

@nplutt It looks like you're using SES? Is that the tool you were planning to use for the incoming message and then I could work on a Lambda to process it for this task? Is there a dev environment or steps I should know about to run the API locally beyond chalice local?

Add navigation header to the website so that users can navigate from the home page to the preferences page and vice versa.

@nplutt I'm willing to help out. This was the first on your list, but let me know if I should grab something else.

Problem

When going to the preferences page without using the link from the sign up email it infinitely loads

Expected

Detects that token is missing and either prompts to go to your confirmation email and click the button that links with the token included in the URL or have a secure way to get a token using your email address without having to find the confirmation email

How to reproduce

Go to https://covid-vaccine-notifications.org/preferences without a token in the URL query string

Notes

A quick fix to at least return an error would be adding a check for the token before calling the API in the UI

    async componentDidMount() {
        let params = (new URL(window.location.href)).searchParams;
        let token = params.get('token');
        if (token) {
            // rest of the code

or have the API catch and send an error back to get into the catch block

(or both)

@nplutt

If a user hasn't updated their profile in the past 21 days, they should no longer be notified of new vaccine appointments. The reason being, that after 21 days one of the two things has probably happened:

1. The user has been able to book an appointment and the vaccine appointment emails are unwanted and become annoying
2. The emails were never reaching the user or they were being sent to their junk mail

The easiest way to do this would be to filter users out on the backend in the find_users_to_notify_for_location method before sending the emails to them.

This could also be done by setting a TTL on the user's updated_at attribute in DynamoDB but since the Terraform isn't in this repo yet, we'll hold off on that for now.