Skip to content
This repository has been archived by the owner on Feb 15, 2023. It is now read-only.

Errors unhandled in ORM #32

Open
alexanderlperez opened this issue Feb 27, 2018 · 1 comment
Open

Errors unhandled in ORM #32

alexanderlperez opened this issue Feb 27, 2018 · 1 comment

Comments

@alexanderlperez
Copy link

alexanderlperez commented Feb 27, 2018

Another dev I'm working with ended up hunting for half-an-hour looking for a reason why an activity wasn't triggering as expected, turns out there was a typo in the field.

However, definitely something avoidable if errors were accessible from the mongoose hooks. Right now they end up unhandled:

doc.populate(paths, function(err, docP) {
if (docP.wasNew) {
stream.FeedManager.activityCreated(docP);
}
});

@dwightgunning
Copy link
Contributor

Thanks for the report.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants