Thanks to visit codestin.com
Credit goes to github.com

Skip to content
This repository was archived by the owner on Jun 30, 2022. It is now read-only.
This repository was archived by the owner on Jun 30, 2022. It is now read-only.

"botskills refresh" should use inlineTriggerUtterances when updating #1872

@lauren-mills

Description

@lauren-mills

Is your feature request related to a problem? Please describe.

Today, if you run botskills refresh, there is no way to handle the updated .lu files for different skills being in different places. There is only one "--luisFolder" parameter and it can't be automated since the path isn't in config.

What is the solution you are looking for?

If botskills refresh used the inlineTriggerUtterances endpoint of the skills (e.g. http://bfcalendarskill.azurewebsites.net/api/skill/manifest?inlineTriggerUtterances=true) to refresh, adding the utterances to the dispatch directly, we wouldn't have to provide the .lu file location to get the latest updates.

This would enable the update_cognitive_models.ps1 script to rebuild the .dispatch file based on the config, which would help in a distributed dev environment.

What alternatives have you considered?

Is there any other context you can provide?

I'm not sure what is needed to compile the utterances into a consumable format for the dispatch tool, but I think they can be parsed into a tabbed file as an input.

Edit: The dispatch tool can accept either a tsv file or txt file with the utterances directly in the --filePath parameter.

--filePath [Required only if type is file] Path to tsv file containing two tab delimited fields in each line representing intent and utterance or .txt file containing one utterance on each line with the file name representing intent name

Metadata

Metadata

Assignees

Labels

Language: TypescriptThis issue is specifically related to C# implementations.Status: BacklogThis will go in the product backlog

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions