You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-reference-node.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1435,7 +1435,7 @@ Use a hook to execute code at different points in the Azure Functions lifecycle.
1435
1435
1436
1436
### Invocation hooks
1437
1437
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:
1439
1439
1440
1440
# [JavaScript](#tab/javascript)
1441
1441
@@ -1453,16 +1453,16 @@ The `PreInvocationContext` object has the following properties:
1453
1453
1454
1454
| Property | Description |
1455
1455
| --- | --- |
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. |
1458
1458
| **`invocationContext`** | The [invocation context](#invocation-context) object passed to the function. |
1459
1459
| **`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. |
1460
1460
1461
1461
The `PostInvocationContext` object has the following properties:
1462
1462
1463
1463
| Property | Description |
1464
1464
| --- | --- |
1465
-
| **`inputs`** | The arguments passed to this specific invocation. |
1465
+
| **`inputs`** | The arguments passed to the invocation. |
1466
1466
| **`result`** | The result of the function. Changes to this value affect the overall result of the function. |
1467
1467
| **`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. |
1468
1468
| **`invocationContext`** | The [invocation context](#invocation-context) object passed to the function. |
@@ -1472,7 +1472,7 @@ The `PostInvocationContext` object has the following properties:
1472
1472
1473
1473
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.
1474
1474
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.
0 commit comments