Closed soupdiver closed 6 years ago
I have fixed this issue in my fork now. Thanks again for pointing it out. It was a lot bigger issue in my fork because I have added more error handling to mongodb-rest.
I'll be publishing to to npm in about a week so that's when you can expect to see these changes live.
thanks :+1:
Superseded by #45
records is 1 or 0 and not the document updated, that's why we can't access _id Check if we got an error and if yet log it Then check if result is 1, which indicates the document was updated, and if yes write the response