-
Notifications
You must be signed in to change notification settings - Fork 23
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
Tracking - Queryable Content Types in Rust #1403
Labels
enhancement
New feature or request
Comments
This was referenced Dec 19, 2024
cameronvoell
added a commit
that referenced
this issue
Dec 20, 2024
Part of #1403 Adds fields to `group_messages` table corresponding to `ContentTypeId` proto and saves them when sending and receiving messages. `ContentTypeId` for reference: https://github.com/xmtp/proto/blob/404a0f41a6dc00f5de5fcfc24856c8b4e417fe59/proto/mls/message_contents/content.proto#L10-L16 ```proto // ContentTypeId is used to identify the type of content stored in a Message. message ContentTypeId { string authority_id = 1; // authority governing this content type string type_id = 2; // type identifier uint32 version_major = 3; // major version of the type uint32 version_minor = 4; // minor version of the type } ```
cameronvoell
added a commit
that referenced
this issue
Dec 21, 2024
Part of #1403 Adds the ability to pass in a vec of content types to the bindings_ffi find_messages function: https://github.com/xmtp/libxmtp/blob/2601bb947cf732baa21fb118fc024012b9da8324/bindings_ffi/src/mls.rs#L1255-L1263
This was referenced Jan 3, 2025
cameronvoell
added a commit
that referenced
this issue
Jan 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See XIP 48 Queryable content Types in Rust: xmtp/XIPs#74
Readable only flagcontent type filtering on messages FFI functions FFI Bindings filter messages by content type #1440 adds content type filter libxmtp update xmtp-android#358Describe the solution to the problem
No response
Describe the uses cases for the feature
No response
Additional details
No response
The text was updated successfully, but these errors were encountered: