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
@@ -353,7 +349,7 @@ If you already have a Web PubSub instance in your Azure subscription, you can sk
353
349
```
354
350
---
355
351
356
-
# [JavaScript-V3](#tab/javascript)
352
+
# [JavaScript Model v3](#tab/javascript)
357
353
- Update `negotiate/function.json` to include an input binding [`WebPubSubConnection`](reference-functions-bindings.md#input-binding), with the following json code.
358
354
```json
359
355
{
@@ -393,7 +389,7 @@ If you already have a Web PubSub instance in your Azure subscription, you can sk
393
389
func new --template "Azure Event Hub trigger" --name messagehandler
394
390
```
395
391
396
-
# [Javascript-V4](#tab/javascript_v4)
392
+
# [JavaScript Model v4](#tab/javascript_v4)
397
393
Update `src/functions/messagehandler.js` to add [Web PubSub output binding](reference-functions-bindings.md#output-binding) with the following json code. We use variable `%hubName%` as the hub name for both IoT eventHubName and Web PubSub hub.
398
394
399
395
```js
@@ -440,7 +436,7 @@ If you already have a Web PubSub instance in your Azure subscription, you can sk
440
436
```
441
437
---
442
438
443
-
# [JavaScript](#tab/javascript)
439
+
# [JavaScript Model v3](#tab/javascript)
444
440
- Update _messagehandler/function.json_ to add [Web PubSub output binding](reference-functions-bindings.md#output-binding) with the following json code. We use variable `%hubName%` as the hub name for both IoT eventHubName and Web PubSub hub.
0 commit comments