Brent Abrahams

Just check that the `query` object has an `_id` value set (the transactions package ignores everything else in the object). That query isn't treated like a true mongo selector (at...

Hmmm... not sure what to suggest here. That code looks fine to me. Note: the return value from the method shown above will not be the return value from the...

Thank you for the comprehensive analysis of the problem and my apologies for the weakness in the package. This certainly needs addressing. If possible, can I take a look at...

This is just a for-the-record, and has no impact on the issue at hand, but at some stage I changed the schema for `deleted` from unix timestamp to ISO Date....

Right. The package should automatically extend any schema for you. I'm going to try to reproduce the error with test and then go from there. I'd thought the whole `items`...

I think it's reasonable too, with a note in the CHANGELOG or README that backwards compatibility might be affected. I'm pretty ignorant about the right way to handle and propagate...

Hi Andreas, Thanks for the kind words. Now, before going too far down the road with this package, there are some things to consider: 1) It **doesn't** use MongoDB 4.x...

Yes, good point. If you've got someone who can put a PR together, I'll happily merge it.

What would happen in that case is the transactions package would only look at fields in the `tx` value, ignoring the rest of the top level fields in the main...

You're quite right. The original options don't get passed on to the mutator methods. That's an omission on my part - consequence of not using TDD and trying to write...