Legacy API

Solution

Installing:

git clone https://github.com/StudentFinance/challenge-rafaelgou.git

npm install
# or
yarn install

To run:

npm start
# or
yarn start

To test:

npm test
# or
yarn test

To develop (restarting on changing files):

npm dev
# or
yarn dev

Problem

There's this legacy API that contains info gathered across decades of existence. Your team needs to use one of the endpoints of that API to build a new web app.

The problem is that this specific endpoint returns millions of items, paginated at 100 per page.

Since you will need more flexibility in terms of page size, your team decides to build a frontend for this legacy API that will allow a user defined value for the number of items per page.

You'll be in charge of this task.

Here's what you need to do:

• Create a simple API with just one required endpoint: GET /items.
• This new API will return the list of items of the legacy API, but will accept a page and perPage arguments returning accordingly.

Here's what you need to know:

• The legacy API is at http://sf-legacy-api.now.sh
• A simple GET /items will return the first 100 items.
• To go to a specific page you use GET /items?page=20 for instance.
• The response will contain info about the total number of items, and the link to the next page.

Guidelines

Here's the important stuff that we take into account when reviewing this exercise:

• It should be simple to start your solution
• It should contain some setup instructions
• It should work correctly
• It should have an automated way to prove it's working correctly

Ideally we want this exercise to take you no more than 90 minutes. You can use this time limit to infer the level of polish we expect from your solution.

Delivery

You will be given access to a github repository to work on your exercise. To submit your solution, open a pull request against the master branch. Use the body of the pull request to briefly describe your solution, what might be incomplete and why, etc.