Page MenuHomePhabricator

Implement translation of raw string from notification into SQLite database entities.
ClosedPublic

Authored by marcin on May 10 2022, 2:53 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Nov 11, 5:06 AM
Unknown Object (File)
Fri, Nov 8, 4:51 AM
Unknown Object (File)
Thu, Nov 7, 6:39 AM
Unknown Object (File)
Sat, Nov 2, 10:50 AM
Unknown Object (File)
Sun, Oct 20, 7:38 PM
Unknown Object (File)
Sun, Oct 20, 6:39 PM
Unknown Object (File)
Oct 7 2024, 7:45 PM
Unknown Object (File)
Oct 7 2024, 7:45 PM

Details

Summary

This diff uses functions implemented in ptwo previous diffs to convert raw string into SQlite database entities

Test Plan

No testing plan. Future diffs will provide a code that uses those functions on iOS and Android respectively

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

Update commit message to include diff link

karol added 1 blocking reviewer(s): tomek.

LGTM, I think it would be good if Tomek took a loook.

tomek requested changes to this revision.May 11 2022, 4:49 AM
tomek added inline comments.
native/cpp/CommonCpp/NativeModules/MessageOperationsUtilities/MessageOperationsUtilities.cpp
87–92

In this case if any message is malformed, we stop saving all the messages from an array. What do you think about doing the opposite: even if there are malformed messages, save all the well-formed into the db?

This revision now requires changes to proceed.May 11 2022, 4:49 AM
This revision is now accepted and ready to land.May 12 2022, 1:45 AM

Use prulal form for rawMessageInfosString

Rebase and move to persistent storage utilities