Note: I have posted an issue regarding this on the Waterline repo, but unfortunately, I have not received a simpler solution than my current workaround.
Within my User model, along with default attributes such as createdDate and modifiedDate, I also have custom attributes like emailAddress and password (which are hidden in toJSON()), as well as some associations with other models.
What is the proper method for comparing a JSON-formatted controller response containing a User model instance to a Waterline model instance?
For instance, the following workaround has proven effective:
request
.get('/user/1')
.end(function (err, res) {
expect(res.body).to.deep.equal(
JSON.parse(JSON.stringify( // Workaround for toJSON not stringifying dates
_.cloneDeep( // Workaround for lost associations
testUser.toJSON() // 'testUser' represents a Waterline model instance equivalent to the requested data ('/user/1')
)
))
);
done();
});
Most of my attempts at comparison have failed thus far; either associations are lost (resolved by cloneDeep()) or date strings are being compared to Date objects (resolved by JSON.parse(JSON.stringify())).
Is there a more efficient way to compare JSON with a Waterline model instance, perhaps through a built-in utility?