From 9e910cae5dd78af9ee461ba682df79a69695fffd Mon Sep 17 00:00:00 2001 From: Brant DeBow Date: Thu, 5 Jun 2025 18:16:23 -0400 Subject: [PATCH] Fix the formatting for inlined code snippets --- .../EventIntegrations/README.md | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/src/Core/AdminConsole/Services/Implementations/EventIntegrations/README.md b/src/Core/AdminConsole/Services/Implementations/EventIntegrations/README.md index e26d589a96..96c8992225 100644 --- a/src/Core/AdminConsole/Services/Implementations/EventIntegrations/README.md +++ b/src/Core/AdminConsole/Services/Implementations/EventIntegrations/README.md @@ -204,11 +204,11 @@ Currently, there are integrations / handlers for Slack and webhooks (as mentione - The top level object that enables a specific integration for the organization. - Includes any properties that apply to the entire integration across all events. - - For Slack, it consists of the token: + - For Slack, it consists of the token: - ``` json + ``` json { "token": "xoxb-token-from-slack" } - ``` + ``` - For webhooks, it is `null`. However, even though there is no configuration, an organization must have a webhook `OrganizationIntegration` to enable configuration via @@ -219,17 +219,17 @@ Currently, there are integrations / handlers for Slack and webhooks (as mentione - This contains the configurations specific to each `EventType` for the integration. - `Configuration` contains the event-specific configuration. - - For Slack, this would contain what channel to send the message to: + - For Slack, this would contain what channel to send the message to: - ``` json - { "channelId": "C123456" } - ``` + ``` json + { "channelId": "C123456" } + ``` - - For Webhook, this is the URL the request should be sent to: + - For Webhook, this is the URL the request should be sent to: - ``` json + ``` json { "url": "https://api.example.com" } - ``` + ``` - `Template` contains a template string that is expected to be filled in with the contents of the actual event.