350 lines
27 KiB
JSON
350 lines
27 KiB
JSON
{
|
||
"name": "Basic Node and Express",
|
||
"order": 2,
|
||
"time": "5 hours",
|
||
"helpRoom": "Help",
|
||
"challenges": [
|
||
{
|
||
"id": "587d7fb0367417b2b2512bec",
|
||
"title": "Introduction to the Basic Node and Express Challenges",
|
||
"description": [
|
||
[
|
||
"",
|
||
"",
|
||
"Node.js is a JavaScript tool that allows developers to write backend (server-side) programs in JavaScript. Node.js comes with a handful of built-in modules--small, independent programs--that help facilitate this purpose. Some of the core modules include:<br><br><ul><li>HTTP: a module that acts as a server</li><li>File System: a module that reads and modifies files</li><li>Path: a module for working with directory and file paths</li><li>Assertion Testing: a module that checks code against prescribed constraints</li></ul><br>Express, while not included with Node.js, is another module often used with it. Express runs between the server created by Node.js and the frontend pages of a web application. Express also handles an application's routing. Routing directs users to the correct page based on their interaction with the application.<br><br>While there are alternatives to using Express, its simplicity makes it a good place to begin when learning the interaction between a backend powered by Node.js and the frontend.",
|
||
""
|
||
]
|
||
],
|
||
"releasedOn": "",
|
||
"challengeSeed": [],
|
||
"tests": [],
|
||
"type": "Waypoint",
|
||
"challengeType": 7,
|
||
"isRequired": false,
|
||
"titleEs": "",
|
||
"descriptionEs": [
|
||
[]
|
||
],
|
||
"titleFr": "",
|
||
"descriptionFr": [
|
||
[]
|
||
],
|
||
"titleDe": "",
|
||
"descriptionDe": [
|
||
[]
|
||
]
|
||
},
|
||
{
|
||
"id": "587d7fb0367417b2b2512bed",
|
||
"title": "Meet the Node console",
|
||
"description": [
|
||
"During the development process, is important to be able to check what’s going on in your code. Node is just a javascript environment. Like client side javascript, you can use the console to display useful debug information. On your local machine, you would see the console output in a terminal. On Gomix you can open the logs in the lower part of the screen. You can toggle the log panel if you push the button ‘Logs’ (top-left, under the app name).",
|
||
"To get started, just put the classic Hello World in the console. We recommend to keep the log panel open while working at these challenges. Reading the logs you can be aware of the nature of the errors that may occur."
|
||
],
|
||
"challengeSeed": [],
|
||
"tests": [
|
||
{
|
||
"text" : "<code>\"Hello World\"</code> should be in the console",
|
||
"testString" : "getUserInput => $.get(getUserInput('url') + '/_api/hello-console').then(data => { assert.isTrue(data.passed, '\"Hello World\" is not in the server console'); }, xhr => { throw new Error(xhr.responseText); })"
|
||
}
|
||
],
|
||
"solutions": [],
|
||
"hints": [],
|
||
"type": "backend",
|
||
"challengeType": 0,
|
||
"translations": {}
|
||
},
|
||
{
|
||
"id": "587d7fb0367417b2b2512bee",
|
||
"title": "Start a working Express Server",
|
||
"description": [
|
||
"In the first two lines of the file myApp.js you can see how it’s easy to create an Express app object. This object has several methods, and we will learn many of them in these challenges. One fundamental method is app.listen(<port>). It tells your server to listen on a given port, putting it in running state. You can see it at the bottom of the file. It is inside comments because for testing reasons we need the app to be running in background. All the code that you may want to add goes between these two fundamental parts. Gomix stores the port number in the environemet variable process.env.PORT. Its value is 3000.",
|
||
"Let’s serve our first string ! In Express, routes takes the following structure: app.METHOD(PATH, HANDLER). METHOD is an http method in lowercase. PATH is a relative path on the server (it can be a string, or even a regular expression). HANDLER is a function that Express calls when the route is matched.",
|
||
"Handlers take the form function(req, res) {...}, where req is the request object, and res is the response object. For example, the handler",
|
||
"<code>function(req, res) {</code>",
|
||
"<code> res.send('Response String');</code>",
|
||
"<code>}</code>",
|
||
"will serve the string 'Response String'.",
|
||
"Use the app.get() method to serve the string Hello Express, to GET requests matching the / root path. Be sure that your code works by looking at the logs, then see the results in your browser, clicking the button ‘Show Live’ in the Gomix UI."
|
||
],
|
||
"challengeSeed": [],
|
||
"tests": [
|
||
{
|
||
"text" : "Your app should serve the string 'Hello Express'",
|
||
"testString" : "getUserInput => $.get(getUserInput('url')).then(data => { assert.equal(data, 'Hello Express', 'Your app does not serve the text \"Hello Express\"'); }, xhr => { throw new Error(xhr.responseText); })"
|
||
}
|
||
],
|
||
"solutions": [],
|
||
"hints": [],
|
||
"type": "backend",
|
||
"challengeType": 0,
|
||
"translations": {}
|
||
},
|
||
{
|
||
"id": "587d7fb0367417b2b2512bef",
|
||
"title": "Serve an HTML file",
|
||
"description": [
|
||
"We can respond with a file using the method res.sendFile(<file>).",
|
||
"You can put it inside the app.get('/', ...) route handler. Behind the scenes this method will set the appropriate headers to instruct your browser on how to handle the file you want to send, according to its type. Then it will read and send the file. This method needs an absolute file-path. We recommend you to use the node global variable __dirname to calculate the path.",
|
||
"e.g. absolutePath = __dirname + relativePath/file.ext .",
|
||
"The file to send is /views/index.html. Try to ‘Show Live’ your app, you should see a big HTML heading (and a form that we will use later…), with no style applied.",
|
||
"Note: You can edit the solution of the preceding challenge, or create a new one. If you create a new solution, keep in mind that Express evaluates the routes from top to bottom. It executes the handler for the first match. You have to comment out the preceding solution, or the server will keep responding with a string."
|
||
],
|
||
"challengeSeed": [],
|
||
"tests": [
|
||
{
|
||
"text" : "Your app should serve the file views/index.html",
|
||
"testString" : "getUserInput => $.get(getUserInput('url')).then(data => { assert.match(data, /<h1>.*<\\/h1>/, 'Your app does not serve the expected HTML'); }, xhr => { throw new Error(xhr.responseText); })"
|
||
}
|
||
],
|
||
"solutions": [],
|
||
"hints": [],
|
||
"type": "backend",
|
||
"challengeType": 0,
|
||
"translations": {}
|
||
},
|
||
{
|
||
"id": "587d7fb0367417b2b2512bf0",
|
||
"title": "Serve Static assets",
|
||
"description": [
|
||
"An HTML server usually has one or more directories that are accessible by the user. You can place there the static assets needed by your application (stylesheets, scripts, images). In Express you can put in place this functionality using the middleware express.static(<public-dir-absolute_path>). If don’t know what a midleware is, don’t worry. We’ll discuss about it later in details. Basically middleware are function that intercept route handlers, adding some kind of information. A middleware needs to be mounted using the method app.use([optional-path], <mware function>). The first path argument is optional. If you don’t pass it, the middleware will be executed for all the requests.",
|
||
"Mount the express.static() middleware for all the requests with app.use(). The absolute path to the assets folder is __dirname + /public.",
|
||
"Now your app should be able to serve a CSS stylesheet. From outside the public folder will appear mounted to the root directory. Your front-page should look a little better now"
|
||
],
|
||
"challengeSeed": [],
|
||
"tests": [
|
||
{
|
||
"text" : "Your app should serve asset files from the <code>/public</code> directory",
|
||
"testString" : "getUserInput => $.get(getUserInput('url') + '/style.css').then(data => { assert.match(data, /body\\s*\\{[^\\}]*\\}/, 'Your app does not serve static assets'); }, xhr => { throw new Error(xhr.responseText); })"
|
||
}
|
||
],
|
||
"solutions": [],
|
||
"hints": [],
|
||
"type": "backend",
|
||
"challengeType": 0,
|
||
"translations": {}
|
||
},
|
||
{
|
||
"id": "587d7fb1367417b2b2512bf1",
|
||
"title": "Serve JSON on a specific route",
|
||
"description": [
|
||
"While an HTML server serves (you guessed it ?) HTML, an API serves data. A REST API allows data exchange in a simple way, without the need for clients to know any detail about the server. The client only needs to know where the resource is (the URL), and the action it wants to perform on it (the verb). The GET verb is used when you are fetching some information, without modifying anything. In these days the preferred data format to move these informations around the web is JSON. In few words JSON is a convenient way to represent a JavaScript object as a string, so it can be easily transmitted.",
|
||
"Let’s create a route that responds with JSON at the path (/json). You can do it as usual, with the app.get() method. Inside the route handler use the method res.json(<object>). This method closes the request-response loop, returning the data. Behind the scenes it converts a valid Javascript object into a string. Then sets the appropriate headers to tell your browser that you are serving JSON, and sends the data back. A valid object has the usual structure {key: data}. data can ba a number, a string, a nested objects or an array. data can also be a variable or the result of a function call. It will be evaluated before converting into a string.",
|
||
"Serve the object <code>{message: 'json'}</code> as a response in JSON format, to the GET requests to the route /json. Point your browser to <your-app-url>/json, you should see the message on the screen."
|
||
],
|
||
"challengeSeed": [],
|
||
"tests": [
|
||
{
|
||
"text" : "The endpoint /json should serve the json <code>{\"message\": \"Hello json\"}</code>",
|
||
"testString" : "getUserInput => $.get(getUserInput('url') + '/json').then(data => { assert.equal(data.message, 'Hello json', 'The \\'/json\\' endpoint does not serve the right data'); }, xhr => { throw new Error(xhr.responseText); })"
|
||
}
|
||
],
|
||
"solutions": [],
|
||
"hints": [],
|
||
"type": "backend",
|
||
"challengeType": 0,
|
||
"translations": {}
|
||
},
|
||
{
|
||
"id": "587d7fb1367417b2b2512bf2",
|
||
"title": "Use the .env file",
|
||
"description": [
|
||
"The .env file is an hidden file that is used to pass environment variables to your application. This file is secret, noone but you can access it. In this file you should store data that you want to keep secret. For example you can store API keys from external services or your database URI. You can also use it to store configuration options. Setting that options you can change the behavior of your application, without the need of rewriting some code. The environment variables are accessible from the app as process.env.VAR_NAME. The process.env object is a global Node object. The variables are passed as strings. By convention the variable names are all uppercase, with words separated by _. The .env is a shell file so you don’t need to quote names or values, and there cannot be space around the = e.g. VAR_NAME=value. Usually you will put each variable definition on a separate line.",
|
||
"We are going to use one environment variable as a configuration option. Store the variable MESSAGE_STYLE=uppercase in the .env file. Then change the GET /json route handler so that if process.env.MESSAGE_STYLE equals to \"uppercase\" the response object becomes {message: HELLO JSON}."
|
||
],
|
||
"challengeSeed": [],
|
||
"tests": [
|
||
{
|
||
"text" : "The response of the endpoint /json should change setting the environment variable MESSAGE_STYLE",
|
||
"testString" : "getUserInput => $.get(getUserInput('url') + '/_api/use-env-vars').then(data => { assert.isTrue(data.passed, 'The response of \"/json\" does not change according to MESSAGE_STYLE'); }, xhr => { throw new Error(xhr.responseText); })"
|
||
}
|
||
],
|
||
"solutions": [],
|
||
"hints": [],
|
||
"type": "backend",
|
||
"challengeType": 0,
|
||
"translations": {}
|
||
},
|
||
{
|
||
"id": "587d7fb1367417b2b2512bf3",
|
||
"title": "Implement a Root-level Request Logger Middleware",
|
||
"description": [
|
||
"Before we introduced the express.static() middleware function. Now it’s time to see what middleware is, in more detail. Middleware functions are functions that take 3 arguments: the request object, the response object, and the next function in the application’s request-response cycle. These functions execute some code that can have side effects on the app, and usually add informations to the request or response objects. They can also end the cycle sending the response, when some condition is met. If they don’t send the response, when they are done they start the execution of the next function in the stack. This is triggered calling the 3rd argument next(). More information here in the express documentation.",
|
||
"Look at the following example :",
|
||
"<code>function(req, res, next) {</code>",
|
||
"<code> console.log(\"I'm middleware...\" );</code>",
|
||
"<code> next();</code>",
|
||
"<code>}</code>",
|
||
"Let’s suppose we mounted this function on a route. When a request matches the route, it displays the string “I’m middleware…”. Then it executes the next function in the stack.",
|
||
"In this exercise we are going to build a root-level middleware. As we have seen in challenge 4, to mount a middleware function at root level we can use the method app.use(<mware-function). In this case the function will be executed for all the request. If you want a function to be executed let’s say only for POST request, you could use app.post(<mware-function>). Analogous methods exist for all the http verbs (GET, DELETE, PUT, …).",
|
||
"Build a simple logger. For every request, it should log in the console a string taking the following format : method path - ip. You can get the request method (http verb), the relative route path, and the caller’s ip from the request object, using req.method, req.path and req.ip. Remember to call next() when you are done, or your server will be stuck forever. Be sure to have the ‘Logs’ opened, and see what happens when some request arrives…",
|
||
"Hint: Express evaluates functions in order. This is true for middleware too. If you want it to work for all the routes, it should be mounted before them."
|
||
],
|
||
"challengeSeed": [],
|
||
"tests": [
|
||
{
|
||
"text" : "Root level logger middleware should be active",
|
||
"testString" : "getUserInput => $.get(getUserInput('url') + '/_api/root-middleware-logger').then(data => { assert.isTrue(data.passed, 'root-level logger is not working as expected'); }, xhr => { throw new Error(xhr.responseText); })"
|
||
}
|
||
],
|
||
"solutions": [],
|
||
"hints": [],
|
||
"type": "backend",
|
||
"challengeType": 0,
|
||
"translations": {}
|
||
},
|
||
{
|
||
"id": "587d7fb1367417b2b2512bf4",
|
||
"title": "Chain Middleware to Create a Time Server",
|
||
"description": [
|
||
"Middleware can be mounted at a specific route using app.METHOD('<path>', mware). Middleware can also be chained inside route definition.",
|
||
"Look at the following example :",
|
||
"<code>app.get('/user', function(req, res, next){</code>",
|
||
"<code> req.user = getTheUserSync(); // Hypotetical Synchronous operation</code>",
|
||
"<code> next();</code>",
|
||
"<code>}, function(req, res) {</code>",
|
||
"<code> res.send(req.user)</code>",
|
||
"<code>})</code>",
|
||
"This approach is useful to split the server operations into smaller units. That leads a to a better app structure, and the possibility to reuse code in different places. This approach can be also used to perform some validation on the data. At each point of the middleware stack you can block the execution of the current chain and pass control to functions specifically desinged to handle errors. Or you can pass control to the next matching route, to handle special cases. We will see how in the advanced express section.",
|
||
"In the route app.get('/now', ...) chain a middleware function and the final handler. In the middleware function you should add the current time to the request object in the req.time key. You can use new Date().toString(). In the handler, respond with a json object, taking the structure {time: req.time}.",
|
||
"Hint: The test will not pass if you don’t chain the middleware. If you mount the function somewhere else, the test will fail, even if the output result is correct."
|
||
],
|
||
"challengeSeed": [],
|
||
"tests": [
|
||
{
|
||
"text" : "The /now endpoint should have mounted middleware",
|
||
"testString" : "getUserInput => $.get(getUserInput('url') + '/_api/chain-middleware-time').then(data => { assert.equal(data.stackLength, 2, '\"/now\" route has no mounted middleware'); }, xhr => { throw new Error(xhr.responseText); })"
|
||
},
|
||
{
|
||
"text" : "The /now endpoint should return a time that is +/- 20 secs from now",
|
||
"testString" : "getUserInput => $.get(getUserInput('url') + '/_api/chain-middleware-time').then(data => { var now = new Date(); assert.isAtMost(Math.abs(new Date(data.time) - now), 20000, 'the returned time is not between +- 20 secs from now'); }, xhr => { throw new Error(xhr.responseText); })"
|
||
}
|
||
],
|
||
"solutions": [],
|
||
"hints": [],
|
||
"type": "backend",
|
||
"challengeType": 0,
|
||
"translations": {}
|
||
},
|
||
{
|
||
"id": "587d7fb2367417b2b2512bf5",
|
||
"title": "Get Route Parameter Input from the Client",
|
||
"description": [
|
||
"When building an API, we have to allow users to comunicate us what they want to get from our service. For example, if the client is requesting informations about a user stored in the database, she needs a way to let us know which user she is interested in. One possible way to get this result, is using route parameters. Route parameters are named segments of the URL, delimited by slashes (/). Each segment captures the value of the part of the URL which match its position. The captured values are populated in the req.params object.",
|
||
"<code>route_path: '/user/:userId/book/:bookId'</code>",
|
||
"<code>actual_request_URL: '/user/546/book/6754' </code>",
|
||
"<code>req.params: {userId: '546', bookId: '6754'}</code>",
|
||
"Build an echo server, mounted at the route GET /:word/echo. Respond with a json document, taking the structure {echo: <word>}. You can find the word to be repeated at req.params.word. You can test your route from your browser the address bar, visiting some matching routes, e.g. <your-app-rootpath>/freecodecamp/echo"
|
||
],
|
||
"challengeSeed": [],
|
||
"tests": [
|
||
{
|
||
"text" : "Test 1 : Your echo server should repeat words correctly",
|
||
"testString" : "getUserInput => $.get(getUserInput('url') + '/eChOtEsT/echo').then(data => { assert.equal(data.echo, 'eChOtEsT', 'Test 1: the echo server is not working as expected') }, xhr => { throw new Error(xhr.responseText); })"
|
||
},
|
||
{
|
||
"text" : "Test 2 : Your echo server should repeat words correctly",
|
||
"testString" : "getUserInput => $.get(getUserInput('url') + '/ech0-t3st/echo').then(data => { assert.equal(data.echo, 'ech0-t3st', 'Test 2: the echo server is not working as expected') }, xhr => { throw new Error(xhr.responseText); })"
|
||
}
|
||
],
|
||
"solutions": [],
|
||
"hints": [],
|
||
"type": "backend",
|
||
"challengeType": 0,
|
||
"translations": {}
|
||
},
|
||
{
|
||
"id": "587d7fb2367417b2b2512bf6",
|
||
"title": "Get Query Parameter Input from the Client",
|
||
"description": [
|
||
"Another common way to get input from the client is by encoding the data after the route path, using a Query string. The query string is delimited by a question mark ?, and includes field=value couples. Each couple is separated by an ampersand &. Express can parse the data from the query string, and populate the object req.query. Some character cannot be in URLs, so the query string needs to be encoded. If you use the API from javascript, you can use specific methods to encode/decode the URL.",
|
||
"<code>route_path: '/library'</code>",
|
||
"<code>actual_request_URL: '/library?userId=546&bookId=6754' </code>",
|
||
"<code>req.query: {userId: '546', bookId: '6754'}</code>",
|
||
"Build an API endpoint, mounted at GET /name. Respond with a json document, taking the structure <code>{ name: '<firstname> <lastname>'}</code>. The first and last name parameters should be encoded in a query string e.g. ?first=<firstname>&last=<lastname>.",
|
||
"TIP: In the following exercise we are going to receive data from a POST request, at the same /name route path. If you want you can use the method app.route(<path>).get(<handler>).post(<handler>). This syntax allows you to chain different verb handlers on the same path route. You can save a bit of typing, and have cleaner code."
|
||
],
|
||
"challengeSeed": [],
|
||
"tests": [
|
||
{
|
||
"text" : "Test 1 : Your API endpoint should respond with the correct name",
|
||
"testString" : "getUserInput => $.get(getUserInput('url') + '/name?first=Mick&last=Jagger').then(data => { assert.equal(data.name, 'Mick Jagger', 'Test 1: \"GET /name\" route does not behave as expected') }, xhr => { throw new Error(xhr.responseText); })"
|
||
},
|
||
{
|
||
"text" : "Test 2 : Your APi endpoint should respond with the correct name",
|
||
"testString" : "getUserInput => $.get(getUserInput('url') + '/name?last=Richards&first=Keith').then(data => { assert.equal(data.name, 'Keith Richards', 'Test 2: \"GET /name\" route does not behave as expected') }, xhr => { throw new Error(xhr.responseText); })"
|
||
}
|
||
],
|
||
"solutions": [],
|
||
"hints": [],
|
||
"type": "backend",
|
||
"challengeType": 0,
|
||
"translations": {}
|
||
},
|
||
{
|
||
"id": "587d7fb2367417b2b2512bf7",
|
||
"title": "Use Body-Parser to Parse POST Requests",
|
||
"description": [
|
||
"Besides GET there is another common http verb , it is POST. POST is the default method used to send client data with HTML forms. In the REST convention POST is used to send data to create new items in the database (a new user, or a new blog post). We don’t have a database in this project, but we are going to learn how to handle POST requests anyway.",
|
||
"In these kind of request the data doesn’t appear in the URL, it is hidden in the request body. This is a part of the HTML request, also called payload. Since HTML is text based, even if you don’t see the data, it doesn’t mean that they are secret. The raw content of an HTTP Post is shown below:",
|
||
"<code>POST /path/subpath HTTP/1.0</code>",
|
||
"<code>From: john@example.com</code>",
|
||
"<code>User-Agent: someBrowser/1.0</code>",
|
||
"<code>Content-Type: application/x-www-form-urlencoded</code>",
|
||
"<code>Content-Length: 20</code>",
|
||
"<code>name=John+Doe&age=25</code>",
|
||
"As you can see the body is encoded like the query string. This is the default format used by HTML forms. With Ajax we can also use JSON to be able to handle data having a more complex structure. There is also another type of encoding : multipart/form-data. This one is used to upload binary files.",
|
||
"In this exercise we will use an urlencoded body.",
|
||
"To parse the data coming from POST requests, you have to install a package: the body-parser. This package allows you to use a series of middleware, which can decode data in different formats. See the docs here.",
|
||
"Install the body-parser module in your package.json. Then require it at the top of the file. Store it in a variable named bodyParser.",
|
||
"The middleware to handle url encoded data is returned by bodyParser.urlencoded({extended: false}). extended=false is a configuration options that tells the parser to use the classic encoding. When using it, values can be only strings or arrays. The extended version allows more data flexibility, but is outmatched by JSON. app.use() the function returned by the previous method call. As usual, the middleware must be mounted before all the routes which need it."
|
||
],
|
||
"challengeSeed": [],
|
||
"tests": [
|
||
{
|
||
"text" : "The 'body-parser' middleware should be mounted",
|
||
"testString" : "getUserInput => $.get(getUserInput('url') + '/_api/add-body-parser').then(data => { assert.isAbove(data.mountedAt, 0, '\"body-parser\" is not mounted correctly') }, xhr => { throw new Error(xhr.responseText); })"
|
||
}
|
||
],
|
||
"solutions": [],
|
||
"hints": [],
|
||
"type": "backend",
|
||
"challengeType": 0,
|
||
"translations": {}
|
||
},
|
||
{
|
||
"id": "587d7fb2367417b2b2512bf8",
|
||
"title": "Get Data from POST Requests",
|
||
"description": [
|
||
"Mount a POST handler at the path /name. It’s the same path as before. We have prepared a form in the html frontpage. It will submit the same data of exercise 10 (Query string). If the body-parser is configured correctly, you should find the parameters in the object req.body. Have a look at the usual library example :",
|
||
"<code>route: POST '/library'</code>",
|
||
"<code>urlencoded_body: userId=546&bookId=6754 </code>",
|
||
"<code>req.body: {userId: '546', bookId: '6754'}</code>",
|
||
"Respond with the same JSON object as before: {name: '<firstname> <lastname>'}. Test if your endpoint works using the html form we provided in the app frontpage.",
|
||
"Tip: There are several other http methods other than GET and POST. And by convention there is a corrispondence between the http verb, and the operation you are going to execute on the server. The conventional mapping is :",
|
||
"POST (sometimes PUT) - Create a new resource using the information sent with the request,",
|
||
"GET - Read an existing resource without modifying it,",
|
||
"PUT or PATCH (sometimes POST) - Update a resource using the data sent,",
|
||
"DELETE => Delete a resource.",
|
||
"There are also a couple of other methods which are used to negotiate a connection with the server. Except from GET, all the other methods listed above can have a payload (i.e. the data into the request body). The body-parser middleware works with these methods as well."
|
||
],
|
||
"challengeSeed": [],
|
||
"tests": [
|
||
{
|
||
"text" : "Test 1 : Your API endpoint should respond with the correct name",
|
||
"testString" : "getUserInput => $.post(getUserInput('url') + '/name', {first: 'Mick', last: 'Jagger'}).then(data => { assert.equal(data.name, 'Mick Jagger', 'Test 1: \"POST /name\" route does not behave as expected') }, xhr => { throw new Error(xhr.responseText); })"
|
||
},
|
||
{
|
||
"text" : "Test 2 : Your API endpoint should respond with the correct name",
|
||
"testString" : "getUserInput => $.post(getUserInput('url') + '/name', {first: 'Keith', last: 'Richards'}).then(data => { assert.equal(data.name, 'Keith Richards', 'Test 2: \"POST /name\" route does not behave as expected') }, xhr => { throw new Error(xhr.responseText); })"
|
||
}
|
||
],
|
||
"solutions": [],
|
||
"hints": [],
|
||
"type": "backend",
|
||
"challengeType": 0,
|
||
"translations": {}
|
||
}
|
||
]
|
||
}
|