URL Paths

On static sites (like blogs or documentation sites) a URL's path mirrors the server's filesystem hierarchy.

For example, if the website https://exampleblog.com had a static web server running in its /home directory, then a request to https://exampleblog.com/site/index.html would probably return the file located at /home/site/index.html.

But technically, this is just a convention. The server could be configured to return any file or data given that path.

It's Not Always That Simple

Paths in URLs are essentially just another type of parameter that can be passed to the server when making a request. For dynamic sites and web applications, the path is often used to denote a specific resource or endpoint.

Assignment

The fantasy quest server uses URL paths to denote different "resources". For example,

/issues
/projects

The entire server is hosted at the path /v1/courses_rest_api/learn-http, however, so all requests must be prefixed with that path.

Update the URL in the code to fetch "project" data instead of "user" data.

Use the /v1/courses_rest_api/learn-http/projects path.

const url = "https://api.boot.dev/v1/courses_rest_api/learn-http/users";

// don't touch below this line

import { Project } from "./types";

const apiKey = generateKey();

const response = await fetch(url, {

method: "GET",

mode: "cors",

headers: {

"X-API-Key": apiKey,

"Content-Type": "application/json",

});

const responseData = await response.json();

logProjects(responseData);

function generateKey(): string {

const characters = "ABCDEF0123456789";

let result = "";

for (let i = 0; i < 16; i++) {

result += characters.charAt(Math.floor(Math.random() * characters.length));

}

return result;

}

function logProjects(projects: Project[]) {

for (const project of projects) {

console.log(`Project: ${project.title}, Completed: ${project.completed}`);

}