JS-301-NodeServer
  • Introduction
  • js_library
    • Node Server
      • 00 - Intro
        • 01 - Purpose
        • 02 - Back-End Setup
        • 03 - Terms Cheat Sheet
      • 01 - Server Set up
        • 01 - npm packages
        • 02 - Express Intro
        • 03 - Express code
      • 02 - Development Tools
        • 01 - Nodemon Intro
        • 02 - Postman Intro
        • 03 - Postman set up
      • 03 - Routes Intro
        • 01 - Routes intro
        • 02 - Express Router() intro
        • 03 - Challenge 1
        • 04 - Challenge 2
      • 04 - Database Intro
        • 00 - DB Intro and Set up
          • 00 - DB Intro
          • 01 - PostgreSQL Intro
          • 02 - Install
        • 01 - Sequelize Intro
          • 01 - Sequelize intro
          • 02 - Initialize
      • 05 - Model View Controller
        • 01 - MVC
          • 00 - MVC Intro
        • 02 - Models
          • 01 - Intro to Models
          • 02 - Test Model
        • 03 - Controllers
          • 00 - Controllers Intro
          • 01 - Controller Set up
          • 02 - Create Method
          • 03 - req.body()
          • 04 - Crafting the Response
          • 05 - Sending the Response
          • 06 - JSON Response
          • 07 - Error Handling
        • 04 - Conclusion
      • 06 - Tokenization
        • 01 - JWT Intro
          • 01 - JWT intro
        • 02 - User Create
          • 01 - User Create
          • 02 - Refactor
        • 03 - User Token
          • 01 - JWT Package
          • 02 - Adding JWT
          • 03 - ENV
      • 07 - Encryption
        • 01 - bcrypt
        • 02 - bcrypt setup
      • 08 - Session
        • 00 - Session Intro
        • 01 - Sign In Method
        • 02 - Sign In Bcrypt
        • 03 - Sign In JWT
      • 09 - Middleware
        • 01 - Test Client HTML
        • 02 - Test Client JS
        • 03 - Middleware intro
        • 04 - Headers intro
        • 05 - Server Update
        • 06 - Test Post
        • 07 - Test Post Refactor
        • 08 - Post Data
        • 09 - Fetch From One
      • 10 - Authenticated Routes
        • 01 - Intro to Authenticated Routes
        • 02 - Validate Session
        • 03 - Changes to app.js
        • 04 - authtestcontroller.js
        • 05 - Delete an Item
        • 06 - Update an Item
        • 07 - Postman Testing
      • 11 - Authenticated Requests
        • 00 - Additions to index
        • 01 - Anatomy of a Request
        • 02 - Create User
        • 03 - Getting a Token
        • 04 - Get Items From One User
        • 05 - Creating an Item for a User
        • 06 - Get one item
        • 07 - Update an Item
        • 08 - Deleting an Item
        • 09 - Deleting with a Custom Event
      • 12 - Workout Log Server
        • 00 - Intro
      • 13 - More Sequelize Functions
        • Migrations
          • 00 - Intro
          • 01 - init and config
          • 02 - Creating the First Migration
          • 03 - Running Migrations
          • 04 - Reverting Migrations
          • 05 - Seeds
          • 06 - Reverting Seeds
        • Queries
          • 00 - Intro
          • 01 - Queries
Powered by GitBook
On this page
  • Overview
  • The Code
  • Analysis
  • Testing
  • Summary of the Flow
  1. js_library
  2. Node Server
  3. 05 - Model View Controller
  4. 03 - Controllers

06 - JSON Response

In this module, we'll return the response as JSON instead of a simple string.

Overview

We now have a proper sequence and a response with some of the stored data, but what if we want to know when the data was stored? We have that in the information in the database, but at the moment it is not coming back in the response. How do we do that? Let's look.

The Code

Go into the testcontroller.js file and add the following method. Add it to the bottom of the file above the export statement.

/*********************
 * Route 6: Return response as JSON
 **********************/
router.post('/six', function (req, res) {
  var testData = req.body.testdata.item;
  TestModel
    .create({
      testdata: testData
    })
    .then(
      function message(testdata) {
        res.json({ //1
          testdata: testdata  //2
        });
      }
    );
});

Analysis

  1. In our callback, rather than res.send(), we will invoke the .json() method. This will, of course, package our response as json.

  2. The same object that was added to the database is now being sent back to the client and stored in a testdata property.

Testing

Let's use Postman to test this: 1. Make sure your server is running. 2. Open Postman. 3. Open a new request. 4. Change the dropdown to POST. 5. Enter the endpoint into the URL: http://localhost:3000/test/six. 6. Click on the body tab under the url input field. 7. Choose the raw radio button. 8. In the dropdown, choose JSON (application/json). 9. In the empty space add, a JSON object like the one below:

{
    "testdata":{
        "item":"step 6"
    }
}
  1. Press send.

  2. You should see the following:

  3. Notice that the data in the response matches the data in the request, but we are also getting back a full JSON object from the database, including timestamp data.

  4. You should also go to Postgres and make sure that the data is there and that the testdata column matches the request and response:

Summary of the Flow

In this module, the following flow is happening:

1. We make a POST request with Postman.

2. body-parser breaks the request into JSON.

3. The router sends the request to the testcontroller.

4. The controller with the /six endpoint is called.

5. The req.body.testdata.item is captured in the testData variable.

6. We then use the Sequelize create() method to create the object to be sent to the DB.

7. The object is sent and Postgres stores it.

8. After the data is stored, we fire the then() method, which returns a Promise.

9. We call a method that takes in a parameter called testdata. It holds the data for the response.

10. The method sends the data back as JSON this time, and the response goes to Postman.

Previous05 - Sending the ResponseNext07 - Error Handling

Last updated 7 years ago

screenshot
screenshot