hatchways / team-carbonara Goto Github PK

Create Appointment Model

Appointment

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

Create the skeleton for the dashboard page

• navbar
• main content

When time is selected, confirm time and schedule (create appointment BE)

• Not in mocks, create a dialog for confirmation

• Email

• Name

• Confirm button

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

Sendgrid

When i run the client npm i then start i get an error after attempting to login (i get a proxy error between 3000 and 3001 local host.) I am not sure how to do the server part because their are no server folders. Thank you

After the onboarding routes for the backend and onboarding frontend is done, integrate

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

Add environment variables to GitHub Actions or CircleCI

https://help.github.com/en/actions/configuring-and-managing-workflows/using-environment-variables
https://circleci.com/docs/2.0/env-vars/

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

store tokens and expiry time from src/App.js user.getAuthResponse()
check gcal api requests

Past Appointments (Events)

Create Model for Meeting

Meeting

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

Gating feature: creating new calendar
Standard: you only get the default

• You shouldn’t see “new meeting” button
  Premium: you can create as many calendar as you want
• FE: If not premium, hide new meeting button

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.

From the upgrade page, when user is directed to this checkout page, they will be able to upgrade their account

After confirmation of appointment on FE, actually create the appointment

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

Integrate user's meetings controller

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)

• CREATE /meeting -> Create a meeting
• GET /meetings -> list of meetings for logged in user

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

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

On calendar view, have the ability to change your timezone.

On change, it should re-render the time availability based on the selected timezone.
For example, by default if my timezone is EST, then I see an available slot for 9am.
If I change it to PST, then it will rerender and now I see an available slot for 6am

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},
...
]

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

• 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 as session

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

Send email confirmation after success of appointment. This may be dependent of ticket: #39