You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new hook functionality by @abraxas potentiall makes the old '.create' method unnecessary.
Idea behind '.create' was to provide a hook by calling 'create' on the new object. With a afterBuild hook, this is not necessary anymore. Maybe it can be removed.
The text was updated successfully, but these errors were encountered:
I would rather keep the create functionality. It's the reason I added the
hooks. We use a wrapped copy of the sequelize model so create will work.
The hooks allow us to create related models by acquiring the id after
create finishes. Our test suite is populated by extended base models in a
big json object we just pass to a helper function.
On Nov 30, 2014 6:40 AM, "Jens Kanschik" [email protected] wrote:
Idea behind '.create' was to provide a hook by calling 'create' on the new
object. With a afterBuild hook, this is not necessary anymore. Maybe it can
be removed.
—
Reply to this email directly or view it on GitHub #8.
The new hook functionality by @abraxas potentiall makes the old '.create' method unnecessary.
Idea behind '.create' was to provide a hook by calling 'create' on the new object. With a afterBuild hook, this is not necessary anymore. Maybe it can be removed.
The text was updated successfully, but these errors were encountered: