Closed
Bug 1867606
Opened 5 months ago
Closed 5 months ago
Make message non nullable in logging API
Categories
(Fenix :: General, task, P3)
Tracking
(firefox123 fixed)
RESOLVED
FIXED
123 Branch
| Tracking | Status | |
|---|---|---|
| firefox123 | --- | fixed |
People
(Reporter: rsainani, Assigned: rsainani)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Currently the message param is nullable in LogSink. Since we want to log a message along with other optional information, it makes sense to make message non optional in the API. All usages of LogSink and Logger actually do specify the message.
|
Assignee | |
Updated•5 months ago
|
Severity: -- → N/A
Priority: -- → P3
|
|
Assignee | |
Updated•5 months ago
|
Assignee: nobody → rsainani
Status: NEW → ASSIGNED
|
||
Comment 1•5 months ago
|
||
|
|
||
Comment 2•5 months ago
|
||
Authored by https://github.com/rahulsainani
https://github.com/mozilla-mobile/firefox-android/commit/1640dc0f9019e4232bb136a82de775756afd96bb
[main] Bug 1867606 - Make message param logging api non nullable
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
status-firefox122:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
|
||
Updated•5 months ago
|
status-firefox122:
fixed → ---
status-firefox123:
--- → fixed
Target Milestone: 122 Branch → 123 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•