Interaction Model creation doesn't support child-only locales for Dialogflow #147
Conversation
This file contains hidden or 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
… when generating the utterances files for Dialogflow
|
Code Climate has analyzed commit 48f052d and detected 0 issues on this pull request. View more on Code Climate. |
armonge
approved these changes
Dec 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It is possible to create a Dialogflow agent that only has the specific locale, such as en-AU and not the parent locale of just
en. This change allows the developer to define another parameter in their project in the interaction.json that forces the Voxa-CLI to ignore the parent locale behavior and only generate the utterances and entity files for the specific locale.