-
Notifications
You must be signed in to change notification settings - Fork 428
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
Mam inbox unification #3165
Mam inbox unification #3165
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3165 +/- ##
==========================================
- Coverage 80.27% 80.23% -0.05%
==========================================
Files 396 396
Lines 32260 32251 -9
==========================================
- Hits 25896 25875 -21
- Misses 6364 6376 +12
Continue to review full report at Codecov.
|
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.
Looks good in general, I have two minor remarks.
cc3ef05
to
35d274a
Compare
If inbox is nothing more than a low-cost summary of mam, we can expect inbox to store pretty much what is stored in mam, and nothing else.
35d274a
to
23b5221
Compare
23b5221
to
d99449c
Compare
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.
Nice, it's good to see the things unified.
If inbox is nothing more than a low-cost summary of mam, we can expect inbox to store pretty much what is stored in mam, and nothing else.
This is currently not true, as inbox is not taking into account
no-store
hints for example, and it is storing body-less messages, like for example it would store carbon copies.Additionally, make both take the
<store>
hint as enforcing storage.