.toJSON()

Purpose

This method also returns a cloned model instance. This one however includes all instance methods. Be sure to read the notes on this one.

Overview

Return Value

Description Possible Data Types
Cloned Record { }

Example Usage

  1. User.find().exec(
  2.   function(err,myRecord){
  3.     var datUser = myRecord.pop().toObject();
  4.     console.log(datUser);
  5.   });
  7. /* { id: 2,
  8.   createdAt: '2013-10-31T22:42:25.459Z',
  9.   updatedAt: '2013-11-01T20:12:55.534Z',
  10.   name: 'Hank',
  11.   phoneNumber: '101-150-1337' } */
  13. User.find().exec(
  14.   function(err,myRecord){
  15.     var datUser = myRecord.pop().toJSON();
  16.     console.log(datUser);
  17.   });
  19. /* { id: 2,
  20.   createdAt: '2013-10-31T22:42:25.459Z',
  21.   updatedAt: '2013-11-01T20:12:55.534Z',
  22.   name: 'Hank' } */
  26. // Don't forget to handle your errors

For model

  1. module.exports = {
  2.   attributes: {
  3.     name: 'string',
  4.     phoneNumber: 'string',
  6.     // Override the default toJSON method
  8.     toJSON: function() {
  9.       var obj = this.toObject();
  10.       delete obj.phoneNumber;
  11.       return obj;
  12.     }
  13.   }
  14. }

Notes

The real power of toJSON relies on the fact every model instance sent out via res.json is first passed through toJSON. Instead of writing custom code for every controller action that uses a particular model (including the “out of the box” blueprints), you can manipulate outgoing records by simply overriding the default toJSON function in your model.
You would use this to keep private data like email addresses and passwords from being sent back to every client.

This is an instance method. Currently, instance methods ARE NOT TRANSACTIONAL. Because of this, it is recommended that you use the equivalent model method instead.