Skip to content

Latest commit

 

History

History
52 lines (36 loc) · 1.99 KB

Assignment.md

File metadata and controls

52 lines (36 loc) · 1.99 KB

Step 1

Using React display at /calendar the calendar availability returned by the API /availability (you can start the server with node server)

API Spec:

GET /availability

Response structure:

An example:

{ "date": "15/10/2019",
  "availableSlots": [
         { "startTime": "9:00", "endTime": "10:00" },
         { "startTime": "10:00", "endTime": "11:00" },
   ]
},
{ "date": "16/10/2019",
  "availableSlots": [
         { "startTime": "15:00", "endTime": "16:00" },
         { "startTime": "16:00", "endTime": "17:00" },
   ]
},
]

UI Spec:

The UI should look like the one in Availability calendar.png (given the time limits don't worry too much about small details)

Scenarios

  • When the /calendar page is loaded the days of the current week should be displayed (no need to display the arrows for scrolling between day) and the days returned from the availability API should be highlighted (in the image with a darker gray)
  • When the user select a day in the calendar the available times returned from the API (availableSlots) should be displayed

Step 2

In `server/index.js instead of using the method generateMockUpResponse use the menthod generateOffice365Schedule passing this week start and end date and tranform the response in the format described above.

Business rules:

Suggestions

  • do small steps and try to think in terms of small incremental scenarios
  • commit often and if you want keep track of your decisions in a separate file called decisions.md so it's easier for us to understand why you made some technical decisions. Don't write too much into it just a few pointers while you build the app
  • see what you can do in max 3 hours, we are not expecting you too finish the assignment in 3 hours