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
There are some inconsistencies with the provider hierarchy: the ChatIntentProvider extends RuntimeIntentProvider, meaning that platforms extending chat cannot use a webhook to receive user inputs.
The quick fix used for now is to define an empty RuntimeIntentProvider subclass (see React platform) that dynamically create a WebhookProvider and registers it to the server.
This should be properly solved by setting ChatIntentProvider as an interface, allowing to consider both RuntimeIntentProviders and WebhookProviders as chat providers.
)
ChatPlatform now contains 2 providers that extend the ones from the runtime component:
- ChatIntentProvider that can be extended by providers based on third-party libraries (e.g. Slack)
- JsonWebhookChatIntentProvider that can be extended by providers receiving messages as JSON payloads
gdaniel
added a commit
to xatkit-bot-platform/xatkit-slack-platform
that referenced
this issue
Sep 3, 2019
There are some inconsistencies with the provider hierarchy: the
ChatIntentProvider
extendsRuntimeIntentProvider
, meaning that platforms extending chat cannot use a webhook to receive user inputs.The quick fix used for now is to define an empty
RuntimeIntentProvider
subclass (see React platform) that dynamically create aWebhookProvider
and registers it to the server.This should be properly solved by setting
ChatIntentProvider
as an interface, allowing to consider bothRuntimeIntentProviders
andWebhookProviders
as chat providers.This issue is related to #220
The text was updated successfully, but these errors were encountered: