Victor Parmar

Duplicate of #33

Hi @doverradio Sorry for the delay in responding to this. From the error `TypeError: Customers is not a constructor`, it seems that your `Customers` class has not been defined properly....

@caltuntas I'll have a look at this again. The merge request you reference actually incorrectly mentioned the issue in question. I cannot guarantee how fast I'll be able to develop...

@caltuntas I had a look at this issue again and while implementing it would be possible, it would vastly complicate the code (and potentially break the current encrypted field naming...

Added test: https://github.com/wheresvic/mongoose-field-encryption/blob/036917d580e0d43c28f3331d0025af439d6ee18c/test/test-db.js#L212

@mexusbg there is a test that uses exactly this example and it is working fine: https://github.com/wheresvic/mongoose-field-encryption/blob/036917d580e0d43c28f3331d0025af439d6ee18c/test/test-db.js#L212 the only difference I see from the example code is the way the `saltGenerator`...

Hi @ArielGavrielov Did you try just doing a `findOne` without the `populate`? As you can see from this test https://github.com/wheresvic/mongoose-field-encryption/blob/036917d580e0d43c28f3331d0025af439d6ee18c/test/test-db.js#L297, `findOne` works normally as is. If you want to use...

Hi and sorry for the delay in responding to this. The issue at hand is that mfe does a `JSON.stringify` on a non-string field which then explodes in size for...

Hi @doguhanokumus This looks good but we definitely need a few tests to verify that the feature works as expected. If you can add them, I'd be happy to merge....

Hi @Yeh35 Thank you very much for taking the time to make this change! I am curious about this use case - if the field is empty then it really...