-
Notifications
You must be signed in to change notification settings - Fork 378
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
feat: Customized functions in runtime should pass validation and be allowed to start bot #4356
Conversation
…llowed to start bot
Current in master, I think we ignore the error of undefined functions, right? So some customer may not aware of they are using a customized functions. So can we at least make sure we don't break MeetAssitant, maybe give them a list of functions they need to add? And we also need to have the error message clear and helpful saying that they need to add unknown functions in settings. |
@lei9444 can you address conflicts please |
Composer/packages/lib/indexers/src/validations/expressionValidation/validation.ts
Outdated
Show resolved
Hide resolved
ping @lei9444 |
FYI @zxyanliu. let's add docs work item to explain this new feature |
overriding the E2E test failure. It looks like a cache issue with the devops agent. |
FYI. The doc on this feature has been merged to master. The content will go live soon. |
Hi @zxyanliu |
…llowed to start bot (microsoft#4356) * feat: Customized functions in runtime should pass validation and be allowed to start bot * update the error message * fix comment * add * match for custom function Co-authored-by: Chris Whitten <christopher.whitten@microsoft.com>
Description
Add a settings field "customizedFunctions" to allow user to config a list of functions name that is customized and should be ignored in validation phase.
Task Item
closes #3656
refs #3130
Screenshots