@@ -92,19 +92,6 @@ Once the message format is ready:
9292 - Make sure to get all required information from users to create your destination type
9393 - See Teams implementation for reference (webhook URL configuration)
9494
95- ## Migration Strategy
96-
97- The system currently supports both:
98-
99- - Legacy ` BaseIntegration ` implementations (e.g., Slack)
100- - New ` BaseMessagingIntegration ` implementations (e.g., Teams)
101-
102- This dual support allows for a gradual migration path where:
103-
104- 1 . New integrations are implemented using ` BaseMessagingIntegration `
105- 2 . Existing integrations can be migrated one at a time
106- 3 . The legacy ` BaseIntegration ` will eventually be deprecated
107-
10895## Implementing a New Integration
10996
11097To add a new messaging platform integration:
@@ -120,10 +107,9 @@ To add a new messaging platform integration:
120107
121108# # Current Implementations
122109
123- - ** Teams** : Uses the new `BaseMessagingIntegration` system with webhook support and Adaptive Cards format
124- - ** Slack** : Currently uses the legacy `BaseIntegration` system (planned for migration)
110+ - ** Teams** : Webhook support, Adaptive Cards format
111+ - ** Slack** : Webhook and token support, Block Kit format
125112
126113# # Future Improvements
127114
128- 1 . Complete migration of Slack to `BaseMessagingIntegration`
129- 2 . Add support for more messaging platforms
115+ 1 . Add support for more messaging platforms
0 commit comments