Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Hook result data shouldn't have sequelize info

See original GitHub issue

When using hooks on sequelize services hook.result has a lot of extra properties on it then just the data. This makes modifying the result data confusing.

Issue Analytics

State:
Created 8 years ago
Comments:12 (6 by maintainers)

Top GitHub Comments

2reactions

ekryskicommented, Aug 25, 2016

@petermikitsh @bedeoverend we have been talking about doing a breaking change to both feathers-sequelize and feathers-mongoose so that services are initialized with {raw: true} and {lean: true} respectively. @daffl saw some pretty massive performance improvements with using lean vs. without.

1reaction

marshallswaincommented, Mar 7, 2016

This is the expected result of using an ORM. That data can be really useful in other scenarios, so it’s generally better to use Sequelize’s methods to convert the model instance to an object. See here for ways of doing this:

http://stackoverflow.com/questions/21961818/sequelize-convert-entity-to-plain-object