Introduce QM_OR_ELSE_LOG and use it in places where QM_OR_ELSE_WARN would spam the reports
Categories
(Core :: Storage: Quota Manager, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox90 | --- | fixed |
People
(Reporter: janv, Assigned: janv)
References
Details
Attachments
(4 files)
This is a follow-up for bug 1701346. Originally, we converted QM_OR_ELSE_WARN back to ordinary orElse, but we now see that it's better to use macros in all cases. We just need a new macro that doesn't report to console/browser console/telemetry.
| Assignee | ||
Comment 1•5 years ago
|
||
| Assignee | ||
Comment 2•5 years ago
|
||
This is more consistent with other cases where we either use QM_OR_ELSE_WARN or
QM_OR_ELSE_NOTE. We will later change some uses of QM_OR_ELSE_LOG to
QM_OR_ELSE_LOG_IF. The switch from custom OrElseIf to Result::orElseIf will be
easier when we don't use OrElseIf directly.
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Comment 3•5 years ago
|
||
Depends on D115055
| Assignee | ||
Comment 4•5 years ago
|
||
Depends on D115159
Comment 6•5 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/8f0fff2a8865
https://hg.mozilla.org/mozilla-central/rev/0c5cdbcd703a
https://hg.mozilla.org/mozilla-central/rev/f85776cea45d
https://hg.mozilla.org/mozilla-central/rev/03de354b3a73
Description
•