parse-server: Files and GeoPoints not correctly saved in ParseConfig since Parse Server version 2.2.7

Issue Description

Files and GeoPoints created in ParseConfig are saved with incorrect types. Types change to String and Array respectively after a refresh.

Steps to reproduce

1. Open Parse dashboard >> Config >> Create Parameter
2. Create a parameter of type “File” having any name and select an arbitrary image
3. Upon creation, parameter shows correct type and image can be opened
4. Upon refreshing the page, the data type changes to string and image can no longer be opened!

For GeoPoint, select type “GeoPoint” in step 2 and enter any valid latitude and longitude. In step 4, type changes to array after refreshing.

Expected Results

Sample result from parse.com or Parse Server version 2.2.6

 {
    "params": {
      "backgroundImage": {
        "__type": "File",
        "name": "tfss-0086e03d-660f-4a53-bee1-6dfb0e1d6906-Tulips.jpg",
        "url": "http://files.parsetfss.com/9499f1cb-d3b8-4514-aa10-05659741bacc/tfss-0086e03d-660f-4a53-bee1-6dfb0e1d6906-Tulips.jpg"
      },
      "eventLocation": {
        "__type": "GeoPoint",
        "latitude": 37.79215,
        "longitude": -122.390335
      }
    }
}

Actual Outcome

{
    "params": {
      "backgroundImage": "ca58066b323f840fbad7e27c88976d9d_tfss-0086e03d-660f-4a53-bee1-6dfb0e1d6906-Tulips.jpg",
      "eventLocation": [
        "-122.390335",
        "37.79215"
      ]
    }
}

Environment Setup

• Server
  • parse-server version: 2.2.7 <= version <= 2.2.13 (last worked normally in 2.2.6
  • Operating System: ?
  • Hardware: ?
  • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): Reproduced on openshift and back4apps
• Database
  • MongoDB version: Tested with 3.2.4 and 3.2.6
  • Storage engine: ?
  • Hardware: ?
  • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): MongoDB@localhost

Logs/Trace

You can turn on additional logging by configuring VERBOSE=1 in your environment.

Not available