-
Notifications
You must be signed in to change notification settings - Fork 9
[PM-20957] Update UniFFI to 0.29.1 #256
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
base: main
Are you sure you want to change the base?
Conversation
Great job, no security vulnerabilities found in this Pull Request |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #256 +/- ##
==========================================
+ Coverage 69.56% 69.61% +0.05%
==========================================
Files 213 218 +5
Lines 16644 16617 -27
==========================================
- Hits 11578 11568 -10
+ Misses 5066 5049 -17 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-20957
📔 Objective
This replaces the renovate PR as the changes are fairly big.
Update UniFFI to version 0.29.1. This requires bumping MSRV to 1.82, as that's the requirement from UniFFI.
The migration consists of a few parts:
UniffiCustomTypeConverter
by the simplercustom_type!
macro. Note that for types defined in other crates, we still use the same macro, but with theremote,
value added.ffi_converter_forward!
:use_remote_type!
uniffi::deps::log
by thelog
crate directly.LinkedId
, I've noticed that we had two implementations ofTryFrom<U32>
, the one used by uniffi based on deserialize, and a hardcoded map. I've combined them in one using the deserialize strategy.I've tested this on the Android and iOS native apps, and they both compile and decrypt the vault without issues.
⏰ Reminders before review
team
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmedissue and could potentially benefit from discussion
:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes