-
Notifications
You must be signed in to change notification settings - Fork 0
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: add useExportItemChat
hook
#203
Conversation
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.
As mentioned, I think it will be wiser to export the chat as a file directly from the back with a mutation. The logic could be included in the export data functions (export action, export as zip) as well. To discuss with @juancarlosfarah and @dialexo .
@@ -78,6 +78,8 @@ export const buildGetItemInvitationsForItemRoute = (id: UUID) => | |||
`${ITEMS_ROUTE}/${id}/invitations`; | |||
|
|||
export const buildGetItemChatRoute = (id: UUID) => `${ITEMS_ROUTE}/${id}/chat`; | |||
export const buildExportItemChatRoute = (id: UUID) => | |||
`${ITEMS_ROUTE}/${id}/export/chat`; |
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.
chat/export
?
a51e6ee
to
4245c0d
Compare
330b7d2
to
eaaf7ca
Compare
I updated this PR with the deprecation of the immutable types exported by query-client. closes #235 |
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.
🍾
This PR adds a hook to get the export chat data from the backend.
closes #202
closes #235