Skip to content

Commit 092562f

Browse files
committed
tweaks
1 parent 05f5619 commit 092562f

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/azure-functions/functions-reference-node.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1435,7 +1435,7 @@ Use a hook to execute code at different points in the Azure Functions lifecycle.
14351435
14361436
### Invocation hooks
14371437
1438-
Invocation hooks are executed once per invocation of your function, either before in a `preInvocation` hook or after in a `postInvocation` hook. By default your hook executes for all trigger types, but you can also filter by type. The following example registers invocation hooks and filters by trigger type:
1438+
Invocation hooks are executed once per invocation of your function, either before in a `preInvocation` hook or after in a `postInvocation` hook. By default your hook executes for all trigger types, but you can also filter by type. The following example shows how to register an invocation hook and filter by trigger type:
14391439
14401440
# [JavaScript](#tab/javascript)
14411441
@@ -1453,16 +1453,16 @@ The `PreInvocationContext` object has the following properties:
14531453
14541454
| Property | Description |
14551455
| --- | --- |
1456-
| **`inputs`** | The arguments passed to this specific invocation. |
1457-
| **`functionHandler`** | The function handler for this specific invocation. Changes to this value affect the function itself. |
1456+
| **`inputs`** | The arguments passed to the invocation. |
1457+
| **`functionHandler`** | The function handler for the invocation. Changes to this value affect the function itself. |
14581458
| **`invocationContext`** | The [invocation context](#invocation-context) object passed to the function. |
14591459
| **`hookData`** | The recommended place to store and share data between hooks in the same scope. You should use a unique property name so that it doesn't conflict with other hooks' data. |
14601460
14611461
The `PostInvocationContext` object has the following properties:
14621462
14631463
| Property | Description |
14641464
| --- | --- |
1465-
| **`inputs`** | The arguments passed to this specific invocation. |
1465+
| **`inputs`** | The arguments passed to the invocation. |
14661466
| **`result`** | The result of the function. Changes to this value affect the overall result of the function. |
14671467
| **`error`** | The error thrown by the function, or null/undefined if there's no error. Changes to this value affect the overall result of the function. |
14681468
| **`invocationContext`** | The [invocation context](#invocation-context) object passed to the function. |
@@ -1472,7 +1472,7 @@ The `PostInvocationContext` object has the following properties:
14721472
14731473
App hooks are executed once per instance of your app, either during startup in an `appStart` hook or during termination in an `appTerminate` hook. App terminate hooks have a limited time to execute and don't execute in all scenarios.
14741474
1475-
The Azure Functions runtime currently [doesn't support](https://github.com/Azure/azure-functions-host/issues/8222) context logging outside of an invocation. Use the Application Insights [npm package](https://www.npmjs.com/package/applicationinsights) to log information during app hooks.
1475+
The Azure Functions runtime currently [doesn't support](https://github.com/Azure/azure-functions-host/issues/8222) context logging outside of an invocation. Use the Application Insights [npm package](https://www.npmjs.com/package/applicationinsights) to log data during app level hooks.
14761476
14771477
The following example registers app hooks:
14781478

0 commit comments

Comments
 (0)