-
Notifications
You must be signed in to change notification settings - Fork 220
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(chatffi): get conversationalists #5849
feat(chatffi): get conversationalists #5849
Conversation
/// ## Safety | ||
/// The `ConversationalistsVector` should be destroyed after use | ||
#[no_mangle] | ||
pub unsafe extern "C" fn get_conversationalists( |
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.
I am missing the create and destroy test for this function in fn test_retrieving_conversationalists_from_vector
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.
The destroy is used in the test_retrieving_conversationalists_from_vector
.
As for a get_conversationlists
test it gets harder because it requires a whole running client/db/service etc. Which I haven't setup for any of the unit testing in chat. It is covered in cucumber though.
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.
Looks good, just one comment ^^
Description
Add a feature to fetch a list of TariAddresses that a client currently has conversations with. This is any address a message has been sent to or received from.
Motivation and Context
Without being about to fetch a list of addresses a client has conversations with, the client can't actually fetch any independent conversations, as conversations are fetched with an address id.
How Has This Been Tested?
New test additions
What process can a PR reviewer use to test or verify this change?
Changes are pretty standard throughout. Handler/Service/DB updates.
Breaking Changes