build: update peer dependencies for Angular v7 (0.7.0) (#220)

Author: wardbell

CHANGELOG.md

@@ -9,6 +9,11 @@ because this is a development tool, not a production product.
 We do try to tell you about such changes in this `CHANGELOG.md`
 and we fix bugs as fast as we can.
 
+<a id="0.7.0"></a>
+## 0.7.0 (2018-10-31)
+
+* update to support Angular v7.
+* no functional changes
 
 <a id="0.6.1"></a>
 ## 0.6.1 (2018-05-04)

README.md

@@ -60,7 +60,7 @@ in the manner of a RESTy web api.
 It natively handles URI patterns in the form `:base/:collectionName/:id?`
 
 Examples:
-```
+```ts
   // for requests to an `api` base URL that gets heroes from a 'heroes' collection 
   GET api/heroes          // all heroes
   GET api/heroes/42       // the hero with id=42
@@ -143,7 +143,7 @@ to ensure that the in-memory backend provider supersedes the Angular version.
 
 * In production, you want HTTP requests to go to the real server and probably have no need for the _in-memory_ provider.
 CLI-based apps can exclude the provider in production builds like this:
-  ```javascript
+  ```ts
   imports: [
     HttpClientModule,
     environment.production ?
@@ -282,13 +282,13 @@ or reset the in-memory database.
 When the last segment of the _api base path_ is "commands", the `collectionName` is treated as the _command_.
 
 Example URLs:
-```
+```sh
   commands/resetdb   // Reset the "database" to its original state
   commands/config    // Get or update this service's config object
 ```
 
 Usage:
-```
+```sh
   http.post('commands/resetdb', undefined);
   http.get('commands/config');
   http.post('commands/config', '{"delay":1000}');
@@ -302,7 +302,7 @@ calls your `InMemoryDbService` data service's  [`createDb` method](#createDb) wi
 enabling the `createDb` logic to adjust its behavior per the client request.
 
 In the following example, the client includes a reset option in the command request body:
-```
+```ts
 http
   // Reset the database collections with the `clear` option
   .post('commands/resetDb', { clear: true }))
@@ -334,17 +334,17 @@ Read the source code for the complete story.
 Configuring the `apiBase` yields the most interesting changes to `parseRequestUrl` behavior:
 
 * For `apiBase=undefined` and `url='http://localhost/api/customers/42'`
-    ```
+    ```ts
     {apiBase: 'api/', collectionName: 'customers', id: '42', ...}
     ```
 
 *  For `apiBase='some/api/root/'` and `url='http://localhost/some/api/root/customers'`
-    ```
+    ```ts
     { apiBase: 'some/api/root/', collectionName: 'customers', id: undefined, ... }
     ```
 
 *  For `apiBase='/'` and `url='http://localhost/customers'`
-    ```
+    ```ts
     { apiBase: '/', collectionName: 'customers', id: undefined, ... }
     ```
 

backend.service.d.ts

@@ -108,7 +108,7 @@ export declare abstract class BackendService {
      * @param resOptionsFactory - creates ResponseOptions when observable is subscribed
      */
     protected createResponseOptions$(resOptionsFactory: () => ResponseOptions): Observable<ResponseOptions>;
-    protected delete({collection, collectionName, headers, id, url}: RequestInfo): ResponseOptions;
+    protected delete({ collection, collectionName, headers, id, url }: RequestInfo): ResponseOptions;
     /**
      * Find first instance of item in collection by `item.id`
      * @param collection
@@ -135,7 +135,7 @@ export declare abstract class BackendService {
     protected genIdDefault<T extends {
         id: any;
     }>(collection: T[], collectionName: string): any;
-    protected get({collection, collectionName, headers, id, query, url}: RequestInfo): ResponseOptions;
+    protected get({ collection, collectionName, headers, id, query, url }: RequestInfo): ResponseOptions;
     /** Get JSON body from the request object */
     protected abstract getJsonBody(req: any): any;
     /**
@@ -187,8 +187,8 @@ export declare abstract class BackendService {
      * To replace this default method, assign your alternative to your InMemDbService['parseRequestUrl']
      */
     protected parseRequestUrl(url: string): ParsedRequestUrl;
-    protected post({collection, collectionName, headers, id, req, resourceUrl, url}: RequestInfo): ResponseOptions;
-    protected put({collection, collectionName, headers, id, req, url}: RequestInfo): ResponseOptions;
+    protected post({ collection, collectionName, headers, id, req, resourceUrl, url }: RequestInfo): ResponseOptions;
+    protected put({ collection, collectionName, headers, id, req, url }: RequestInfo): ResponseOptions;
     protected removeById(collection: any[], id: number): boolean;
     /**
      * Tell your in-mem "database" to reset.