-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
Branches: generateMeetingLink-backend
Task at Hand
- Replace
.env
file with new.env
we sent you. The main difference between old.env
and new.env
is that there are multiple Zoom accounts for you to handle, so make sure that you parsed in the appropriate account when you handle the API call. - Browse
app/api/zoom
. Get familiarize with how api are deployed here. Then, navigate to "Create a Meeting" page, which is located inapp/createmeeting/page.tsx
to see how we call these APIs. Make these updates to the APIs:
- For
generateToken.ts
, make sure that you parse in additional prop to decide whether you are trying to get token for ZOOM account 1, 2, 3, or 4. - Make sure that the other APIs that call
generateToken.ts
also reflect this change (i.e. also updateCreateMeeting/index.ts
,DeleteMeeting/index.ts
,UpdateMeeting/index.ts
)
- Browse to test page and find New Meeting Sidebar at the end. Add Generate Meeting Link button.
- When you click the button:
- You should check whether we have Meeting Title, Date, Time, and Zoom Account chosen. If not you should display an error. If yes, create a meeting with those props using appropriate Zoom account.
- You can test by create a meeting, then check if it is the right Zoom account that create it, and if all the right information can be located within the scheduled meeting.
- Confirm that your code and pull request follow the Pull Request Checklist.
Acceptance Criteria
- When a meeting is created, all the information is parsed to it.
- When a meeting is created, the the Zoom Account selected should be the one that create this meeting.