Skip to content

Commit 3162994

Browse files
committed
revert
1 parent 11656e4 commit 3162994

File tree

2 files changed

+520
-22100
lines changed

2 files changed

+520
-22100
lines changed

CONTRIBUTING.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -211,7 +211,7 @@ If your pull request introduces a change that may affect the storage or retrieva
211211
- `it_only_db('mongo')` // will make a test that only runs on mongo
212212
- `it_exclude_dbs(['postgres'])` // will make a test that runs against all DB's but postgres
213213
* Similarly, if your feature is intended to only work with PostgreSQL, you should disable MongoDB-specific tests with:
214-
214+
215215
- `describe_only_db('postgres')` // will create a `describe` that runs only on postgres
216216
- `it_only_db('postgres')` // will make a test that only runs on postgres
217217
- `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:
299299
title: 'Door locked',
300300
warning: 'Anyone can enter your house.',
301301
solution: 'Lock the door.',
302-
check: () => {
302+
check: () => {
303303
return; // Example of a passing check
304304
}
305305
}),
306306
new Check({
307307
title: 'Camera online',
308308
warning: 'Security camera is offline.',
309309
solution: 'Check the camera.',
310-
check: async () => {
310+
check: async () => {
311311
throw 1; // Example of a failing check
312312
}
313313
}),
@@ -360,7 +360,7 @@ Introducing new [Parse Server configuration][config] parameters requires the fol
360360
2. If the new parameter does not have one single value but is a parameter group (an object containing multiple sub-parameters):
361361
- 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)
362362
- add the parameter group type to `nestedOptionTypes` in [/resources/buildConfigDefinition.js](https://github.com/parse-community/parse-server/blob/master/resources/buildConfigDefinition.js)
363-
363+
364364
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_`.
365365

366366
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
421421
422422
```
423423
fix: remove handle from door
424-
424+
425425
BREAKING CHANGE: You cannot open the door anymore by using a handle. See the [#migration guide](http://example.com) for more details.
426426
```
427427
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
432432
433433
```
434434
revert: fix: remove handle from door
435-
435+
436436
This reverts commit 1234567890abcdef.
437437
```
438438
@@ -448,7 +448,7 @@ If the commit reverts a previous commit, use the prefix `revert:`, followed by t
448448
instead of:
449449
```
450450
revert: ci: add something
451-
451+
452452
This reverts commit 1234567890abcdef.
453453
```
454454
@@ -525,7 +525,7 @@ The following changes are done in the `alpha` branch, before publishing the last
525525
7. Merge PR with "squash and merge", do not do a "merge commit":
526526
- Commit message: (use PR title)
527527
- Description: (leave empty)
528-
528+
529529
ℹ️ 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.
530530
8. Delete temporary branch `backmerge`.
531531
10. Create a new temporary branch `backmerge` on branch `beta`.

0 commit comments

Comments
 (0)