-
Notifications
You must be signed in to change notification settings - Fork 3
feat(ffi): add MoveModule, MoveFunction and their inner types as records #91
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
Conversation
|
Conflicts |
| #[derive(Debug, derive_more::From, uniffi::Object)] | ||
| pub struct MoveFunction(pub iota_graphql_client::query_types::MoveFunction); | ||
| #[uniffi::remote(Record)] | ||
| pub struct MoveFunction { |
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.
Maybe we could just append Query to all of the queries for consistency? We should probably do this in the core crate too eventually.
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.
Seems like there is no way to use uniffi::remote(Record) with a different name than in the core crate, so would require this change in the core crate
Don't want to do more changes than needed now, but I agree that this is something to consider
Fixes #59
Had to rename graphql MoveStruct to MoveStructQuery, because it was conflicting with the other one in iota-sdk-types:
error: symbolUNIFFI_META_IOTA_SDK_FFI_RECORD_MOVESTRUCTis already defined