-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor (Webhook)Provider hierarchy #221
Labels
Comments
gdaniel
changed the title
Refactory (Webhook)Provider hierarchy
Refactor (Webhook)Provider hierarchy
May 15, 2019
gdaniel
added a commit
to xatkit-bot-platform/xatkit-chat-platform
that referenced
this issue
Sep 3, 2019
gdaniel
added a commit
to xatkit-bot-platform/xatkit-slack-platform
that referenced
this issue
Sep 3, 2019
gdaniel
added a commit
to xatkit-bot-platform/xatkit-discord-platform
that referenced
this issue
Sep 3, 2019
gdaniel
added a commit
to xatkit-bot-platform/xatkit-react-platform
that referenced
this issue
Sep 3, 2019
gdaniel
added a commit
to xatkit-bot-platform/xatkit-zapier-platform
that referenced
this issue
Sep 4, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: