-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use with Aggregation? #91
Comments
I'am also looking for this. Would be a great feature! I managed to get it working with the aggregate framwork by adding functionality for this is my local node_modules. This of course will be overwritten when you update or do anything else with the installed packaged. So if you use it it will probably needs to be forked or in some other way saved. Also this is not really tested in a good way, I only tried it to fit my specific needs and my data. And to be fair i just copy pasted the original code so i probably missed something. So my strong advice is don't use this in production, but maybe you can tweak it so it will work as you need it. I also didn't try the pagination but the function takes a regular pipeline so it should probably work as normal i guess. If someone has the knowledge and time, it would be very appreciated if that person took a look and developed this code more and tested (or rewrote it completley) and make a PR to this repo. Add this function to
Put this in the bottom of
Usage:
|
Do you want to request a feature, an issue, or report a bug?
A feature
What is the current behaviour?
Doesn't work with aggregate
If the current behaviour is a bug, please provide the steps to reproduce.
What is the expected behaviour?
If this is a feature request, what is the motivation or use case for changing
the behaviour?
Please mention other relevant information such as Node.js and mongoose version.
The text was updated successfully, but these errors were encountered: