-
Notifications
You must be signed in to change notification settings - Fork 369
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
fix: Move skill settings into settings.skillConfiguration #4312
Conversation
…e existing skill object Signed-off-by: Srinaath Ravichandran <srravich@microsoft.com>
Signed-off-by: Srinaath Ravichandran <srravich@microsoft.com>
…soft/BotFramework-Composer into srravich/fix-runtime-start
isSkill: false, | ||
allowedCallers: ['*'], | ||
}, | ||
skill: {}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason to keep this around even though it's empty?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. Its the object to which we append new skills from the UI. I presonally prefer to keep it so that when new bots are created by default it shows as an empty object and we just keep adding to the dictionary.
Signed-off-by: Srinaath Ravichandran <srravich@microsoft.com>
Task Item
Moved skill settings from settings.skill into settings.skillConfiguration. The reason being settings.skill is being used by Composer to maintain the list of skills consumed by the Root Bot. This fix would just allow the C# runtime to get the skills config.
@carlosscastro is tracking this functionality to be ported into the JS runtume
@tonyanziano This is the fix for the faulty skill config
#minor