Victor Parpoil

Thank you ! This PR fix issues I had when updating to 2.7.3, related to aggregate function arguments. ``` MongoInvalidArgumentError: Method "collection.aggregate()" accepts at most two arguments at Collection.aggregate [...]...

The PR referenced fixes the issue but I am not sure of the implications of the modification. Maybe it's better to change the function that is adding fields for deletion...

I found the reason for this. The request is stringified [here](https://github.com/cult-of-coders/grapher/blob/842dbb1ed313ecd1abdd7fc79378be673445df1b/lib/query/counts/genEndpoint.server.js#L21) . Hence, the date object is transformed into a string and the mongo query fails to compare the string...

@StorytellerCZ I updated and resolved conflicts, thank you !

Hi @SpyridonZ, you should provide a reproduction repository to get help on your issue. There is a big chance that this is the result of a misuse of the package.

Can you indicate me which file/function you have in mind ? I have been searching for the `scheduledForDeletion` param in the preparation of the graph but in the case referenced...

Thanks for the insight ! indeed, `_shouldCleanStorage` is called after each linker node is added. Since the `auhtorId` has not been yet added to the CollectionNode, it is marked with...

@theodorDiaconu Here is an updated version modifying the body keys order to add the fields first to the CollectionNode. Let me know if you think it is not the good...

I just bumped into this in one of our apps. Here is the use case : you use the before.update function to compute the field **computed** of the collection with...

Here is a try for an update to the documentation If we want to avoid the multiple calls of `before.update` function when using `multi:true`, I think we will have to...