Aggregate match doesn't work with custom date field

[JeromeDeLeon]

Issue Description

The problem still persist when doing aggregate with customFieldDate as pointed out by this scenario.

This is my scenario of aggregation. I have tried this one using MongoDB Compass to simulate the results and that works.

[
  {
    group: {
      _id: "$shiftId",
      openedAt: {
        $first: "$shift._created_at"
      }
    }
  },
  {
    match: {
      openedAt: {
        $gte: new Date()
      }
    }
  }
]

Steps to reproduce

Create an aggregation similar to above sample.

Expected Results

Empty array

Actual Outcome

Results filtered by openedAt

Environment Setup

• Server

  • parse-server version (Be specific! Don't say 'latest'.) : 3.10.0
  • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): localhost

• Database

  • MongoDB version: 3.4
  • Storage engine: WiredTiger
  • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): localhost

[mtrezza]

This is addressed by #10438 which adds opt-in rawValues and rawFieldNames options for aggregation queries. With rawValues: true, date values are expressed using MongoDB Extended JSON ({ $date: '...' }) instead of relying on schema-based detection. This works for computed fields from $project stages that are not in the schema.