This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
feat: set expected entity when capturing inputs to API calls in .dialog import #1387
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mattmazzola
approved these changes
Nov 25, 2019
LarsLiden
approved these changes
Nov 26, 2019
|
🎉 This PR is included in version 0.412.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For cases where a bot asks the user a question (eg "What is your product key?") whose response will be used as the input to an API call, this PR updates the import flow to
productKey)We later look up the entity by its name when creating actions, and set the expected / suggested entity on the appropriate action.
Tested with the license key bot :