Manuel

I wonder whether storing in log files serves the purpose. To be efficiently searchable in regular audits it would better be stored in a DB. That also allows to easily...

I believe the GDPR auditable information should be logged separately from other server logs; is this going into distinct files? Logging as JSON or CSV is fine I think; then...

@coderabbitai explain the architecture of the audit logging this PR adds. Does it allow to save the GDPR logs into distinct log files? Is the feature and logging output suitable...

> The current architecture could be refactored to use an AuditLogStorageAdapter interface, making the existing file-based implementation one of several available options. That makes sense to me. For example, storing...

@dplewis since you just added eslint (in push adapter), maybe you want to take a look at this; not sure if that's an easy fix?

Closing via https://github.com/parse-community/Parse-SDK-JS/pull/2214

@RahulLanjewar93 happy to review a PR if you open one.

**Fixed: Security concern - removed schema information from client error responses** Changes: - **Removed** `mongoUniqueIndexErrorFormatter()` function (fragile regex parsing) - **Server logs**: Now log the complete MongoDB error message via...

@messagenius-admin pinging since you may want to take a look at the updates in this PR and provide feedback. @dblythy could you please comment on coderabbit review feedbacks rather than...

IIRC `updateMany` does not return which objects have been modified. I cannot think of a way around this that would be scalable and maintain the performance gain of `updateMany` vs....