From 014be36f38009324a896defd5a4b3ea8adcd4b9d Mon Sep 17 00:00:00 2001 From: VaishnaviNandakumar Date: Mon, 15 Jan 2024 19:41:44 +0530 Subject: [PATCH] Added highlighted code --- pages/docs/tutorials/websocket/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/docs/tutorials/websocket/index.md b/pages/docs/tutorials/websocket/index.md index b5d1c4480925..936fd6c359e8 100644 --- a/pages/docs/tutorials/websocket/index.md +++ b/pages/docs/tutorials/websocket/index.md @@ -88,7 +88,7 @@ Your AsyncAPI document needs to be very clear on the type of event it is expecte The `payload` attribute specifies the name, format, and description of all the expected properties. `Heart-Counter` starts the popularity count of a message by validating if the `reaction` property set in the `reaction` schema definition corresponds to "heart". - + {`components: messages: reaction: @@ -188,7 +188,7 @@ In this example, the `helloListener` operation keeps an eye out for the message Your Slack application is designed to be notified of events within your workspace. It does this by subscribing to a specific event type making use of Slack's Event API. So in this case the `action` property in both the operations is set to `receive` events. - + {`operations: helloListener: action: receive