[Track 7/9] Get user

[taki-tiler-server]

Step 1/3 - The request

Estimated time: 2 hours

This is the first GET request you're going to implement on the project. After logging in and creating user, now it's time to provide an endpoint for fetching a user information. Some details:

1. Route: GET /users/:id
2. Path parameter: a user id
3. It must be authenticated
4. Response: a user, the same of the POST /users route.

Unlike the previous tracks, now you're going to write the request prototype and integrate with the database already.

NOTE: don't forget to predict error cases. In this endpoint, the most obvious one is passing an id that is not found on database.

[Gabrielle-Verissimo]

Finish

[taki-tiler-server]

Step 2/3 - The tests

Estimated time: 2 hour

Now it's time to test your request and all its possible scenarios.

Write tests to verify it's working. Again: try to make independent tests, setting up your database before each one according to what you want to test.

[Gabrielle-Verissimo]

Finish

[taki-tiler-server]

Step 3/3 - Challenge: seed

Estimated time: 3 hours

[Spoiler alert]: your next track is about writing a new endpoint to list users. But in order to do that, you should have users on database, right? Well, you could use your recently implemented POST /users to add them. However, this challenge is about presenting you a more efficient method, while you can learn something new: database seed.

The idea is to write some code to populate your database, creating an environment to facilitate your next request. Follow the steps:

1. Create a new script on package.json and name it seeds. Leave it empty, for now.
2. Create a file on a folder of your choice and write some code to add at least 50 users on database. This is going to be your seed script.
3. Think about how you would make it run properly, then return to package.json and create your npm run seeds command.

NOTE: don't forget that you have to connect with the database in order to run the code, right?

You can check on TablePlus (or DBeaver, if you are on a Linux machine) if your script worked.

NOTE 2: this is an example of task that we can use the chore/ prefix on the name of the branch, because it's an auxiliar development task, and not a feature.

[Gabrielle-Verissimo]

Finish

[taki-tiler-server]

Click here for your next track