Craig Condon

Yep, the `data` property is the source of truth, and shouldn't be modified within the Model. Got any ideas on how you'd like this API to be?

The `data` property is still tremendously useful if you have a remote data source. I just wonder if it could either a) be moved to a mixin, or b) defined...

Both collections and models should have the ability to load data asynchronously, you just have to define a `load` method in that case. See my last comment on #63.

I _think_ Sift should work how you want it to -- do you have a pseudocode example?

Does the `compare` option help solve your problem? For example: ```javascript const compare = (a, b) => { if (a instanceof BSONObject && b instanceof BSONObject) { reutrn a.value ===...

happy to include this functionality in sift if you want to create a PR!

Just starting on this functionality in #157. The API will likely be: ```javascript const asyncFilter = sift({ $existsInDb: true }, { operations: { async $existsInDb(expectToExist, name) { const existsInDb =...

Halfway there! Sift is now published as [deno_sift](https://deno.land/x/deno_sift), thanks for the suggestion. The only thing that's left outstanding is to figure out how to publish to NPM & Deno --...

awesome, looking forward to it!

Hey @thardy, there are a few options to do this: you can use [$where](https://github.com/crcn/sift.js#where) as @J3m5 mentioned, or you can add your own [custom behavior](https://github.com/crcn/sift.js#custom-behavior). Let me know if this...