-
Notifications
You must be signed in to change notification settings - Fork 108
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
Extension: Display history of conversation + add public api url to list convos #8348
Conversation
|
case "GET": | ||
const conversations = await getUserConversations(auth); | ||
res.status(200).json({ conversations }); | ||
return; |
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.
Should we update the swagger doc ?
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.
Yes I said it in OP but running npm run docs did not change anything 😬
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.
ok I need to update manually the swagger doc and create the new schema for conversationwithoutcontent
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.
Discussed IRL we don't necessarily want to comm now on it -> need to decide how we expose the ConversationWithoutContent, not a big deal but not blocking and we want to have an MVP 😬
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.
once swagger doc is done / swagger.json updated
Created a task assigned to me to not forget about it: https://github.com/dust-tt/tasks/issues/1568 |
Description
ConversationWithoutContentType
.I need to figure out how to update our api doc, I ran
npm run docs
but did not change anything, will dig. Can be reviewed already.Risk
Can be rolled back.
Deploy Plan
Deploy front to get the new API route.