-
Notifications
You must be signed in to change notification settings - Fork 11
feat(plugin/faq-analyzer): creation of a FAQ analyzer plugin #61
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
Conversation
I realized that im using table searches / updates on the client rather than on the table itself. I need to reference this: https://botpress.com/docs/api-reference/tables-api/openapi/createTableRows for plugin client (basically just botpress client but typed) I'll update the code when I have a chance. |
Replacing the zod with @bpinternal/zui --> https://www.npmjs.com/package/@bpinternal/zui fixes the e.toTypescript error producing with the zai extract. However, the plugin is still not functioning as expected. |
[BUG]: Latest update adds every question (last and most recent array) --> creating disparity and latency ig |
Fixed issues above. Remaining issues before Im able to start optimizing + making code quality better:
|
* add file sharing upload support * add file support for bloc * Google chat spaces * Clarify where to find webhook url in the readme * Specify the chat return type in client * chore: deploying google-chat-spaces to plus * chore: naming for gcs * feat(devops): integration version checker (#67) * feat(devops): creation of a codeowners file * feat(devops): adding scripts for workflows for checking integration naming * fix(integrations): naming prefix for plus * fix(workflows): checking the integration version in prod without building (because of bp_modules) * fix(workflows): detect changes to JSON as well * chore: version bumping to pass version checker * chore: woops * feat(readme): adding a readme.md to botpress/growth (#76) * fix(bp-integration-runner): updating packages (#74) * fix integration name lookup (#73) --------- Co-authored-by: David Vitor Antonio <[email protected]> Co-authored-by: Matea Vasileski <[email protected]>
Coming soon...