Closed rubdos closed 9 months ago
Attention: 30 lines
in your changes are missing coverage. Please review.
Comparison is base (
1cc7517
) 17.21% compared to head (c5b5662
) 17.07%.:exclamation: Current head c5b5662 differs from pull request most recent head e42688c. Consider uploading reports for the commit e42688c to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Let's ship it, I think I had a bit more quality of life improvements to add, but I can do it later! Thanks for this 😄
FYI, this is 100% untested. I probably want to ship some more things, but https://gitlab.com/whisperfish/whisperfish/-/merge_requests/530 is on hold currently until after release :'-)
(This is more becoming the "let's just implement it damnit" merge request)
(This is more becoming the "let's just implement it damnit" merge request)
In order to avoid this, I'll cut this PR short on just some "minor" PNI/ACI refactoring, such that https://gitlab.com/whisperfish/whisperfish/-/merge_requests/530#02abb4bfed1d40529ab2bc6cfe9338119e97be98 is also mergable. Continuation in #285.
Branch as I go along, with things that I disagree with :'-)
One thing I disagree with, but don't necessarily want to fix here:
set_next_prekey_id
sounds like a great source of confusion. In RDBMS-based implementations, thenext_prekey_id
-family is expected to just query the database and return max+1. Setting a value doesn't make any sense, but the naming of the method implies it should need to be a method with a side effect.