revert

CONTRIBUTING.md

@@ -211,7 +211,7 @@ If your pull request introduces a change that may affect the storage or retrieva
   - `it_only_db('mongo')` // will make a test that only runs on mongo
   - `it_exclude_dbs(['postgres'])` // will make a test that runs against all DB's but postgres
 * Similarly, if your feature is intended to only work with PostgreSQL, you should disable MongoDB-specific tests with:
-
+ 
   - `describe_only_db('postgres')` // will create a `describe` that runs only on postgres
   - `it_only_db('postgres')` // will make a test that only runs on postgres
   - `it_exclude_dbs(['mongo'])` // will make a test that runs against all DB's but mongo
@@ -299,15 +299,15 @@ Adding a new security check for your feature is easy and fast:
             title: 'Door locked',
             warning: 'Anyone can enter your house.',
             solution: 'Lock the door.',
-            check: () => {
+            check: () => {    
               return;     // Example of a passing check
             }
           }),
           new Check({
             title: 'Camera online',
             warning: 'Security camera is offline.',
             solution: 'Check the camera.',
-            check: async () => {
+            check: async () => {  
               throw 1;     // Example of a failing check
             }
           }),
@@ -360,7 +360,7 @@ Introducing new [Parse Server configuration][config] parameters requires the fol
 2. If the new parameter does not have one single value but is a parameter group (an object containing multiple sub-parameters):
    - add the environment variable prefix for the parameter group to `nestedOptionEnvPrefix` in [/resources/buildConfigDefinition.js](https://github.com/parse-community/parse-server/blob/master/resources/buildConfigDefinition.js)
    - add the parameter group type to `nestedOptionTypes` in [/resources/buildConfigDefinition.js](https://github.com/parse-community/parse-server/blob/master/resources/buildConfigDefinition.js)
-
+  
     For example, take a look at the existing Parse Server `security` parameter. It is a parameter group, because it has multiple sub-parameter such as `checkGroups`. Its interface is defined in [index.js][config-index] as `export interface SecurityOptions`. Therefore, the value to add to `nestedOptionTypes` would be `SecurityOptions`, the value to add to `nestedOptionEnvPrefix` would be `PARSE_SERVER_SECURITY_`.
 
 3. Execute `npm run definitions` to automatically create the definitions in [/src/Options/Definitions.js][config-def] and [/src/Options/docs.js][config-docs].
@@ -421,7 +421,7 @@ If the pull request contains a breaking change, the commit message must contain
 
   ```
   fix: remove handle from door
-
+  
   BREAKING CHANGE: You cannot open the door anymore by using a handle. See the [#migration guide](http://example.com) for more details.
   ```
   Keep in mind that in a repository with release automation, merging such a commit message will trigger a release with a major version increment.
@@ -432,7 +432,7 @@ If the commit reverts a previous commit, use the prefix `revert:`, followed by t
 
   ```
   revert: fix: remove handle from door
-
+  
   This reverts commit 1234567890abcdef.
   ```
 
@@ -448,7 +448,7 @@ If the commit reverts a previous commit, use the prefix `revert:`, followed by t
   instead of:
   ```
   revert: ci: add something
-
+  
   This reverts commit 1234567890abcdef.
   ```
 
@@ -525,7 +525,7 @@ The following changes are done in the `alpha` branch, before publishing the last
 7. Merge PR with "squash and merge", do not do a "merge commit":
    - Commit message: (use PR title)
    - Description: (leave empty)
-
+  
    ℹ️ Merging this PR will not trigger a release; the back-merge will not appear in changelogs of the `beta`, `alpha` branches; the back-merged fix will be an undocumented change of these branches' next releases; if necessary, the change needs to be added manually to the pre-release changelogs *after* the next pre-releases.
 8. Delete temporary branch `backmerge`.
 10. Create a new temporary branch `backmerge` on branch `beta`.