docs: remove compatibility references; add deployment guide (parse-co…

…mmunity#871)
dblythy · May 14, 2022 · 88bd1f3 · 88bd1f3
1 parent e663a09
commit 88bd1f3
Show file tree

Hide file tree

Showing 30 changed files with 318 additions and 394 deletions.
diff --git a/_includes/android/objects.md b/_includes/android/objects.md
@@ -30,7 +30,7 @@ After this code runs, you will probably be wondering if anything really happened
 
 ```javascript
 objectId: "xWMyZ4YEGZ", score: 1337, playerName: "Sean Plott", cheatMode: false,
-createdAt:"2011-06-10T18:33:42Z", updatedAt:"2011-06-10T18:33:42Z"
+createdAt:"2022-01-01T12:23:45.678Z", updatedAt:"2022-01-01T12:23:45.678Z"
 ```
 
 There are two things to note here. You didn't have to configure or set up a new Class called `GameScore` before running this code. Your Parse app lazily creates this Class for you when it first encounters it.

diff --git a/_includes/arduino/objects.md b/_includes/arduino/objects.md
@@ -36,7 +36,7 @@ response.close(); // Free the resource
 After this code runs, you will probably be wondering if anything really happened. To make sure the data was saved, you can look at the Data Browser in your app on Parse. You should see something like this:
 
 ```javascript
-	objectId: "xWMyZ4YEGZ", temperature: 175.0, leverDown: true, createdAt: "2011-06-10T18:33:42Z", updatedAt: "2011-06-10T18:33:42Z"
+	objectId: "xWMyZ4YEGZ", temperature: 175.0, leverDown: true, createdAt: "2022-01-01T12:23:45.678Z", updatedAt: "2022-01-01T12:23:45.678Z"
 ```
 
 There are two things to note here. You didn't have to configure or set up a new Class called `Temperature` before running this code. Your Parse app lazily creates this Class for you when it first encounters it.
@@ -106,7 +106,7 @@ create.setClassName("TestObject");
 create.add("number", 42.0);
 create.add("foo", "bar");
 create.addGeoPoint("location", 40.0, -30.0);
-create.addJSONValue("dateField", "{ \"__type\": \"Date\", \"iso\": \"2011-08-21T18:02:52.249Z\" }"); create.addJSONValue("arrayField", "[ 30, \"string\" ]");
+create.addJSONValue("dateField", "{ \"__type\": \"Date\", \"iso\": \"2022-01-01T12:23:45.678Z\" }"); create.addJSONValue("arrayField", "[ 30, \"string\" ]");
 create.addJSONValue("objectField", "{ \"number\": 30, \"string\": \"baz\" }");
 create.addJSONValue("emptyField", "null");
 create.send();

diff --git a/_includes/common/data.md b/_includes/common/data.md
@@ -42,8 +42,8 @@ The JSON format is an array of objects in our REST format or a JSON object with
     "score": 1337,
     "playerName": "Sean Plott",
     "cheatMode": false,
-    "createdAt": "2012-07-11T20:56:12.347Z",
-    "updatedAt": "2012-07-11T20:56:12.347Z",
+    "createdAt": "2022-01-01T12:23:45.678Z",
+    "updatedAt": "2022-01-01T12:23:45.678Z",
     "objectId": "fchpZwSuGG"
   }]
 }

diff --git a/_includes/dotnet/objects.md b/_includes/dotnet/objects.md
@@ -30,7 +30,7 @@ After this code runs, you will probably be wondering if anything really happened
 
 ```javascript
 objectId: "xWMyZ4YEGZ", score: 1337, playerName: "Sean Plott", cheatMode: false,
-createdAt:"2011-06-10T18:33:42Z", updatedAt:"2011-06-10T18:33:42Z"
+createdAt:"2022-01-01T12:23:45.678Z", updatedAt:"2022-01-01T12:23:45.678Z"
 ```
 
 There are two things to note here. You didn't have to configure or set up a new Class called `GameScore` before running this code. Your Parse app lazily creates this Class for you when it first encounters it.

diff --git a/_includes/graphql/objects.md b/_includes/graphql/objects.md
@@ -53,8 +53,8 @@ mutation createAGameScore {
       "clientMutationId": "anUniqueId",
       "gameScore": {
         "id": "R2FtZVNjb3JlOjZtdGlNcmtXNnY=",
-        "updatedAt": "2019-12-02T10:14:28.786Z",
-        "createdAt": "2019-12-02T10:14:28.786Z",
+        "updatedAt": "2022-01-01T12:23:45.678Z",
+        "createdAt": "2022-01-01T12:23:45.678Z",
         "playerName": "Sean Plott",
         "score": 1337,
         "cheatMode": false,

diff --git a/_includes/ios/objects.md b/_includes/ios/objects.md
@@ -51,7 +51,7 @@ After this code runs, you will probably be wondering if anything really happened
 
 ```js
 objectId: "xWMyZ4YEGZ", score: 1337, playerName: "Sean Plott", cheatMode: false,
-createdAt:"2011-06-10T18:33:42Z", updatedAt:"2011-06-10T18:33:42Z"
+createdAt:"2022-01-01T12:23:45.678Z", updatedAt:"2022-01-01T12:23:45.678Z"
 ```
 
 There are two things to note here. You didn't have to configure or set up a new Class called `GameScore` before running this code. Your Parse app lazily creates this Class for you when it first encounters it.

diff --git a/_includes/js/objects.md b/_includes/js/objects.md
@@ -146,7 +146,7 @@ After this code runs, you will probably be wondering if anything really happened
 
 ```json
 objectId: "xWMyZ4YEGZ", score: 1337, playerName: "Sean Plott", cheatMode: false,
-createdAt:"2011-06-10T18:33:42Z", updatedAt:"2011-06-10T18:33:42Z"
+createdAt:"2022-01-01T12:23:45.678Z", updatedAt:"2022-01-01T12:23:45.678Z"
 ```
 
 There are two things to note here. You didn't have to configure or set up a new Class called `GameScore` before running this code. Your Parse app lazily creates this Class for you when it first encounters it.

diff --git a/_includes/js/users.md b/_includes/js/users.md
@@ -417,8 +417,8 @@ With a response body like:
 ```json
 {
   "username": "Parse",
-  "createdAt": "2012-02-28T23:49:36.353Z",
-  "updatedAt": "2012-02-28T23:49:36.353Z",
+  "createdAt": "2022-01-01T12:23:45.678Z",
+  "updatedAt": "2022-01-01T12:23:45.678Z",
   "objectId": "uMz0YZeAqc",
   "sessionToken": "r:samplei3l83eerhnln0ecxgy5",
   "authData": {
@@ -439,7 +439,7 @@ The body of the response will contain the `objectId`, `createdAt`, `sessionToken
 ```json
 {
   "username": "iwz8sna7sug28v4eyu7t89fij",
-  "createdAt": "2012-02-28T23:49:36.353Z",
+  "createdAt": "2022-01-01T12:23:45.678Z",
   "objectId": "uMz0YZeAqc",
   "sessionToken": "r:samplei3l83eerhnln0ecxgy5"
 }

diff --git a/_includes/parse-server/Files-Migration.md b/_includes/parse-server/Files-Migration.md
diff --git a/_includes/parse-server/MongoRocks.md b/_includes/parse-server/MongoRocks.md