Fixed spacing

Author: DrewImm

.github/CONTRIBUTING.md

@@ -8,4 +8,4 @@ Please use our issue-tracker: https://github.com/StatelessStudio/pointyapi/issue
 
 ## Contributing Code
 
-You can contribute code by creating a pull request.  Please create/find an issue for the problem first, and discuss with an administrator.
+You can contribute code by creating a pull request. Please create/find an issue for the problem first, and discuss with an administrator.

CHANGELOG.md

@@ -133,7 +133,7 @@
 
 ## [1.0.0] Feb-27-2019
 
-First major release.  View the migration guide: ([MIGRATION GUIDE](https://github.com/StatelessStudio/pointyapi/blob/master/migration.md))
+First major release. View the migration guide: ([MIGRATION GUIDE](https://github.com/StatelessStudio/pointyapi/blob/master/migration.md))
 
 ### Breaking Changes
 - [Issue #78] Removed response parameter from responder functions

README.md

@@ -296,9 +296,9 @@ npm i pointyapi
 	router.delete(`/:id`, loader, onlySelf, deleteEndpoint);
 	```
 
-	Notice `onlySelf` - that means only the user can access this route.  We're not logged in yet, so we're certainly not "self"
+	Notice `onlySelf` - that means only the user can access this route. We're not logged in yet, so we're certainly not "self"
 
-	Create another router file, `src/routes/auth.ts`.  This will be our authentication route so that we can log-in.
+	Create another router file, `src/routes/auth.ts`. This will be our authentication route so that we can log-in.
 
 	```typescript
 	// src/routes/auth.ts

migration.md

@@ -9,7 +9,7 @@
 ## Version 0.x.x -> 1.x.x
 
 1. Remove `response` parameter from responders and handlers
-	Responders and handlers no longer take a `response` parameter, so you just need to remove the parameter from all calls to the following functions.  This is easiest via find and replace (pro tip: use regex!)
+	Responders and handlers no longer take a `response` parameter, so you just need to remove the parameter from all calls to the following functions. This is easiest via find and replace (pro tip: use regex!)
 	- `response.error()`
 	- `response.conflictResponder()`
 	- `response.deleteResponder()`
@@ -21,7 +21,7 @@
 	- `response.unauthorizedResponder()`
 	- `response.validationResponder()`
 2. Rename hooks
-	Hooks have been renamed for clarity.  Rename all hooks in your models (pro tip: project-wide find & replace).  **Make sure you go in order, and replace all occourences before moving on, because some hook names conflict with old hook names!**
+	Hooks have been renamed for clarity. Rename all hooks in your models (pro tip: project-wide find & replace). **Make sure you go in order, and replace all occourences before moving on, because some hook names conflict with old hook names!**
     - `beforePut()` -> `beforePatch()`
     - `beforeGet()` -> REMOVED
     - `beforeDelete()` -> `delete()`
@@ -43,15 +43,15 @@
 		}
 	});
 	```
-4. Remove `deleteFilter`.  This filter does not have any value
+4. Remove `deleteFilter`. This filter does not have any value
 5. Update import directories
    - `/fork-server` -> `/utils`
    - `/get-identifier-value` -> `/utils`
    - `/listen` -> `/utils`
    - `/run-hooks` -> `/utils`
    - `/upgrade-user-role` -> `/utils`
 6. Update `setModel()` for auth routers
-	Previously, `setModel()` would run the incorrect hooks for auth routers, and may even lead to deleting the wrong user's token.  This has been fixed by passing `true` to the fourth parameter (`isAuth`)
+	Previously, `setModel()` would run the incorrect hooks for auth routers, and may even lead to deleting the wrong user's token. This has been fixed by passing `true` to the fourth parameter (`isAuth`)
 
 	```typescript
 	// Set model
@@ -64,14 +64,14 @@
 	});
 	```
 7. Make sure all hooks are `async` functions
-	Hooks must now be async functions.  Search through hooks, and replace with `public async HOOK_NAME()`
+	Hooks must now be async functions. Search through hooks, and replace with `public async HOOK_NAME()`
 8. Make sure hooks utilize this.
 	Hooks are now bound to the resource, and should utilize `this.` notation
 9. Make sure hooks don't loop
     Hooks are called once per object, therefore they should only take care of one resource at a time
 11. Default resources can now be added via `addResource(User, {...})`
 12. Update GET queries.
-	GET queries have been reworked.  The following field names have changed:
+	GET queries have been reworked. The following field names have changed:
 	- `__select` => `select`
 	- `__whereAnyOf` => `whereAnyOf`
 	- `__search` => `search`
@@ -109,7 +109,7 @@
 17. Remove empty searches.
 	Get queries no longer require a `search` key to access other query keys
 18. All mdoel members must be initialized to undefined, including relational arrays
-19. Queries may no longer pass special keys with `__` or `___`.  You should now put these queries in the `additionalParameters` query object
+19. Queries may no longer pass special keys with `__` or `___`. You should now put these queries in the `additionalParameters` query object
 
 ## Version 1.x.x -> 2.x.x
 
@@ -118,7 +118,7 @@
    1. Make a POST endpoint in your auth router:
 		`router.post('/refresh', loader, refreshTokenEndpoint);` 
    2. Update your front-end auth refreshTokenservice to save the `refreshToken` and `refreshExpiration` from the `loginEndpoint`
-   3. Set a timeout to call the `refreshTokenEndpoint` route when the access token expires. Setup the body like this: `{ __refreshToken: myRefreshToken }`.  This will return an updated user object, including a new access token & expiration time.
+   3. Set a timeout to call the `refreshTokenEndpoint` route when the access token expires. Setup the body like this: `{ __refreshToken: myRefreshToken }`. This will return an updated user object, including a new access token & expiration time.
 3. **(Optional)** PointyAPI now supports `UUID`. Follow the steps in the Readme to enable UUID (strongly recommended for production).
 
    **NOTE** If you are already in production and decide to migrate to UUID, you must make sure to update relations etc

src/bodyguard.ts

@@ -2,7 +2,7 @@
  * # Bodyguards
  *
  * Bodyguards are guards that operate on the body (*request.query,
- * request.body*).  Bodyguards come in two forms:
+ * request.body*). Bodyguards come in two forms:
  * - Guards
  *	- Guards block incoming requests, e.g. a basic user
  *	who tries to delete an admin
@@ -11,7 +11,7 @@
  *
  * ## Decorators
  *
- * Decorators are used to set read/write privelages on your model.  There
+ * Decorators are used to set read/write privelages on your model. There
  * are several decorators already available for you:
  * - Read
  *  - CanRead(who?)
@@ -34,16 +34,16 @@
  *
  * ### BodyguardKey
  *
- * There is one additional decorator: `BodyguardKey`.  This key will be
- * presented to the guards/filters to authorize the request.  For example, the
+ * There is one additional decorator: `BodyguardKey`. This key will be
+ * presented to the guards/filters to authorize the request. For example, the
  * `userId` of a User would be the BodyguardKey, or the `fromUserId` and
- * `toUserId` would be the BodyguardKeys on a Chat model.  When the
+ * `toUserId` would be the BodyguardKeys on a Chat model. When the
  * bodyguard runs, it will compare the authenticated user with the
  * BodyguardKey of the resource.
  *
  * ## How to Use?
  *
- * Guards, Endpoints, and Responders contain bodyguards underneath.  If you
+ * Guards, Endpoints, and Responders contain bodyguards underneath. If you
  * are not writing custom guards or responders, you will only need to set the
  * decorators on your model.
  *

src/database.ts

@@ -11,7 +11,7 @@
  *
  * ## Setting Entities
  *
- * You will need to tell the database what entities to use.  **You should do
+ * You will need to tell the database what entities to use. **You should do
  * this in your `pointy.before` function.**
  * ```typescript
  * import { pointy } from 'pointyapi';
@@ -30,7 +30,7 @@
  * ## Creating Custom Database Drivers
  *
  * You can create a custom database driver class by extending the BaseDb class.
- * You will also need to set the pointyapi database.  You must run
+ * You will also need to set the pointyapi database. You must run
  * TypeORM's `createConnection` function in your `Database::connect()`
  *
  * ```typescript

src/database/base-db.ts

@@ -11,7 +11,7 @@ export class BaseDb {
 	// Database entities
 	public entities: any[] = [ ExampleUser ];
 
-	// Connection name.  Default is "default"
+	// Connection name. Default is "default"
 	public connectionName = 'default';
 
 	// Auto-sync (Empties database on restart, not for production!)

src/database/postgres.ts

@@ -11,7 +11,7 @@ export class PointyPostgres extends BaseDb {
 	/**
 	 * Connect to the database
 	 * @param options Database credentials (pass
-	 * 	a string to load from file, or pass the object directly).  Database
+	 * 	a string to load from file, or pass the object directly). Database
 	 * 	will rely on `process.env.DATABASE_URL` if this is not set.
 	 */
 	public connect(options?: string | Object): Promise<Connection> {

src/endpoints.ts

@@ -2,7 +2,7 @@
  * # Endpoints
  *
  * Endpoints are where the action of a route actually takes place,
- * for example posting a resource or logging in.  The following
+ * for example posting a resource or logging in. The following
  * endpoints come premade:
  * - CRUD
  *  - postEndpoint
@@ -15,7 +15,7 @@
  *
  * ## Using endpoints
  *
- * Endpoints go in your route, after any guards.  You'll have to
+ * Endpoints go in your route, after any guards. You'll have to
  * set a model so the guards and endpoints know what you're working with.
  *
  * ```typescript

src/handlers/error-handler.ts

@@ -4,7 +4,7 @@ import { createTimestamp } from '../utils/create-timestamp';
  * Default error handler
  * @param error Error message/object to send to the client (or
  * 	database error object to check)
- * @param code Error response code to send.  Default is 500
+ * @param code Error response code to send. Default is 500
  */
 export function errorHandler(error: any, code: number = 500): void {
 	// Check for known errors