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
deprecate quick replies in favor of using custom
#5239
Comments
@tmbo what are your thoughts on this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Thinking we should do this for |
Current facebook quick reply format:
with custom:
It's a little more work, but you can also add images to your buttons, as well of tons of other quick reply content types like location, emails, and phone numbers. I expect some people are already using custom to achieve this functionality. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@erohmensing when i try to do
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
➤ Maxime Verger commented: 💡 Heads up! We're moving issues to Jira: https://rasa-open-source.atlassian.net/browse/OSS. From now on, this Jira board is the place where you can browse (without an account) and create issues (you'll need a free Jira account for that). This GitHub issue has already been migrated to Jira and will be closed on January 9th, 2023. Do not forget to subscribe to the corresponding Jira issue! ➡️ More information in the forum: https://forum.rasa.com/t/migration-of-rasa-oss-issues-to-jira/56569. |
Description of Problem: We currently support
quick_replies
in the domain file, though they are only supported on the facebook channel. This leads to a lot of extra code for something that is a pretty specific use case. I thought about this after reconsidering adding them to the SDK, where the support for them never made it in.Overview of the Solution: Now that the same functionality can be accomplished via the
custom
domain key, we can handle facebook quick replies the way that any other channel-specific UI elements are handled.The text was updated successfully, but these errors were encountered: