Closed
Bug 1676079
Opened 4 years ago
Closed 3 years ago
Make marker type names consistent, with "Marker" suffix
Categories
(Core :: Gecko Profiler, task, P3)
Core
Gecko Profiler
Tracking
()
RESOLVED
FIXED
85 Branch
Tracking | Status | |
---|---|---|
firefox85 | --- | fixed |
People
(Reporter: mozbugz, Assigned: mozbugz)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Follow-up to https://phabricator.services.mozilla.com/D96043#inline-542326
Most marker type definitions end with "Marker", e.g. DOMEventMarker
.
The main advantage, is that it's easier to distinguish them from non-profiler data structures in editors and in code browsers like Searchfox. E.g., DOMEvent
may give the idea that this is a DOM event itself, when it's really a profiler marker about DOM events.
However some marker types don't say "Marker", like NoPayload
or Text
.
There are defined in the baseprofiler::markers
namespace, so I initially thought that that would be enough to identify them as markers.
But the namespace may not always be explicit or obvious.
Also, for consistency it would be good to use the same suffix everywhere.
Assignee | ||
Updated•4 years ago
|
Assignee: nobody → gsquelart
Assignee | ||
Comment 1•3 years ago
|
||
Pushed by gsquelart@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/99aa3dc8e185 For consistency and clarity, add Marker suffix to all marker types - r=gregtatum
Comment 3•3 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox85:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 85 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•