hatchways / team-beluga Goto Github PK

Create a route that:

• Loads availability for given day (GET /availability?day=2342343243)
• Returns a list of available slots

Google Calendar API

• /freeBusy timeMin, timeMax 

Each date you select, it’ll load the appointment slots available

[
{start_time: 2323234, end_time: 234234},
{start_time: 2323234, end_time: 234234},
{start_time: 2323234, end_time: 234234},
...
]

Use Material UI Snackbar on success or error with desired message.
We want to be able to use a function like:
showMessage(messageString, messageType)
For example:
showMessage("Login Failed", "error")
showMessage("Event type created successfully", "success")

• CREATE /appointment -> Create an appointment
  • meeting_id, name, email, time (datetime), timezone
• GET /appointments -> list of appointments for logged in user

Set up postgres connection on server

• On every protected route visit, check that cookie is valid and update user

on Creation of user, create an initial Meeting for a 60 min duration (this is default)

Create a form to get a user's email address after they've confirmed a time on the Calendar UI page

https://stripe.com/docs/api/customers/create

https://stripe.com/docs/payments/checkout/subscriptions

Set up a dev account and use the appropriate API keys set up for the app.

• integrate user availability and timezone

Create Appointment Model

Appointment

• event_type_id
• name 
• email 
• time (datetime) 
• timezone

• POST /event-types -> Create an event type
• GET /event-types -> list of event types for logged in user
• PUT /event-types/:id -> Edit
• DELETE /event-types/:id -> Delete

Create Model for Event Types

Event Type

• user_id
• title
• url
• duration (15, 30, 45, 60) -> these are in minutes

• Sign up with email (or test email)
• test it out (create a service that sends an email and test that it works)
• share credentials on Slack

Fetch all future/past appointments (for next/last 30 days).
Display them on the frontend. Maybe with headings for future/past
Show delete icon for future appointments

• create two front-end react routers (login and signup)
• There is no landing page - redirect to signup

Integrate the onboarding pages:

• connect URL textfield with user controller to check if URL is unique
• add field to user model for timezone
• add appropriate fields to the user model for availability

Blacklist JWT on logout

Frontend

• Block off unavailable days
• Preselect the next day 
• Block off time that is unavailable for the user (appointment time slots blocked off state) 
• When time is selected, confirm time and schedule (create appointment BE)

• When user is logged in /signup and /login should redirect to the dashboard
• Make the onboarding show up only once (check if user has their URL filled out, if they have their availability set)
• Add logout button into a menu when clicking user in Navbar
• Make logout button functional (it needs to hit a logout route in the backend)

Upgrade your account

Ignore some information from the mocks. Instead have two blocks:

1. FREE STANDARD (this is by default) no need for payment
2. PREMIUM ACCOUNT (payment) -> leads to Stripe checkout page

Material UI templates

There is no issue creating the first event. However, error occurs when trying to create second event.

From the output of terminal it seems the user_id is missing when creating the second event.

sqlalchemy.exc.DataError: (psycopg2.errors.InvalidTextRepresentation) invalid input syntax for type integer: ""
LINE 1: ...es (user_id, title, url, duration, color) VALUES ('', 'asd',...
^

[SQL: INSERT INTO event_types (user_id, title, url, duration, color) VALUES (%(user_id)s, %(title)s, %(url)s, %(duration)s, %(color)s) RETURNING event_types.id]
[parameters: {'user_id': '', 'title': 'asd', 'url': 'asd', 'duration': 30, 'color': '#3E200B'}]
(Background on this error at: http://sqlalche.me/e/14/9h9h)

Double check whether url is unique when creating event types

replace the fixed name with dynamic name fetching from DB, and also the dashboard

Separate components such as:

• Nav bar
• Main Content

*https://developers.google.com/calendar/quickstart/js

• https://cloud.google.com/nodejs/getting-started/authenticate-users
• https://dev.to/risafj/beginner-s-guide-to-oauth-understanding-access-tokens-and-authorization-codes-2988

• Create User when authentication is success
• Save access token, maintain logged in state on refresh

• look for Flask JWT libraries

• create a JWT, store it in a (httpOnly) cookie

• decorator on the backend that checks whether JWT is valid

• private route make an API call to check if JWT is valid and get the user back

We already know about this and is looking into finding a solution.

Adding this issue for tracking purpose.

• When creating an event type, if we don't change the color and submit, it would give a missing field error alert.
• Rerender cards after adding new eventType
• edit create eventType dialog url InputAdornment

refactor onboarding to change the structure to:

<onboarding>
  ...<children>
</onboarding>

createa. middleware that we can add to routes to ensure it is accessed by authenticated users

Make sure calendar shows correct times for availability

• Store a user's Google Auth token in the User model to enable API calls to Google
• Store user's refresh token, to get a new auth token if necessary

Make a backend route to cancel an appointment

• delete calendar event
• send confirmation email

Once display appointments is done, integrate with frontend

• GET /user/:id/is_unique?url=<> -> checks if url is unique amongst other users

• UPDATE /user/:id -> updates user information

• we are not going to allow editing email (obviously because we're using OAuth with calendar). But we are going to let them edit other parts of their profile (such as availability)

New dialog that allows you to create a new-type for a specific duration

• Check Event Types model to see what fields we need. Add "tag_colour" to model.

Also fix the annoying <p> errors in console 😂

Checkout page that takes card information and upgrades user to selected plan.
Or doesn't take payment information and downgrades user to selected plan

Create a wrapper around <Route/> that checks if the user is logged in and also hits a route in the backend to make sure the token is valid.
If the user is logged in and the token is valid, we go to the <Route/> that is passed in.
If the user is not logged in or the token is not valid, redirect back to /login

Integrate user's event-types controller

There are 3 pages to onboarding

/profile_settings -> unique url and timezone

• check for uniqueness to continue
• storing timezone in UTC
  /confirm -> confirmation of successful connect
  /availability -> setting availability hours and days