Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: “The getSchemas() method returns a JSON key-value pair where the key is the schema’s $id and the value is the JSON schema itself.”

A block of code is set as follows:

{
  "id": 1,
  "name": "Foo",
  "hobbies": [ "Soccer", "Scuba" ]
}

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

"test": "tap --before=test/run-before.js test/**/**.test.js --after=test/run-after.js --no-check-coverage",
"test:coverage": "tap --coverage-report=html --before=test/run-before.js test/**/**.test.js --after=test/run-after.js",

Any command-line input or output is written as follows:

<absolute URI>#<local fragment>

Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: “It is crucial to keep in mind that you should take care of the response status code when you implement your error handler; otherwise, it will be 500 – Server Error by default.”

Tips or Important notes

Appear like this.