mirror of
https://github.com/keiffster/program-y.git
synced 2026-04-03 08:29:42 -06:00
Change restful flask response for OpenChatBot API v2.0 when callback parameter is provided #51
Labels
No labels
News
News
News
News
News
News
News
News
bug
bug
bug
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
enhancement
enhancement
enhancement
enhancement
enhancement
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github/program-y#51
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ohoachuck on 10/17/2020
Hello Keith,
I hope you are doing well, as I see you are less active than you use to be ?
After a long period, I'm getting back to OpenChatBot work and while getting down to your code, I could see the enormous work you have done to be compliant with the format. This is really great!
My plan is to provide with an out of the box running program-y metabot + rich OpenChatBot web client that will be able to chat to any other compatible OpenChatBot frameworks.
Doing so, I was working on my initial web client (available at the swagger page here) that should be able to directly point to program-y restful api V2.2 url.
Then I face 2 issues :
Obviously my fonction name here is
parseocbAnswerSee this StackOverflow link for the kind of issue.
This Pull request is fixing this #1issue. But I know my python code is usually bad and there are may be better or cleaner approaches to handle this. You might have an idea ?
I believe the proper way to handle issue #2 would be to let response['text'] as is (while still providing back media, suggestions, meta, etc.) and use response['channel']['markup'] object to provide with your rendered AIML into HTML for the type "html", and ever better add a new type "aiml" (for markup).
Any feedbacks would be appreciated.
Stay safe.
Olivier.