Closed Bug 1508949 Opened 6 years ago Closed 6 years ago

Implement the "timespan" metric type parser

Categories

(Toolkit :: Telemetry, enhancement, P1)

enhancement
Points:
2

Tracking

()

RESOLVED FIXED
Tracking Status
firefox65 --- affected

People

(Reporter: Dexter, Assigned: Dexter)

References

Details

(Whiteboard: [telemetry:mobilesdk:m3])

Attachments

(1 file)

This bug is about adding the "timespan" type in the glean parsers. See the spec at: https://docs.google.com/document/d/186GI_2ljdqWqWTBk5P3QjHD3BwpMyd8kRayRAuz1-dk/edit#
Assignee: nobody → alessio.placitelli
Blocks: 1491345, 1508948
Points: --- → 2
Priority: -- → P1
Whiteboard: [telemetry:mobilesdk:m3]
Blocks: 1508950
No longer blocks: 1508950
Blocks: 1508952
No longer blocks: 1508952
Assignee: alessio.placitelli → tlong
The parser for the timespan metric is already implemented in the glean parser project.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
(In reply to Travis Long from comment #1) > The parser for the timespan metric is already implemented in the glean > parser project. I think there's something that must be done in this bug: the timespan's metric definition accepts a "Resolution" parameter. This should be defined as an enum or something like that in the parser. See `Lifetime` for a related example: https://github.com/mozilla/glean_parser/search?q=Lifetime&unscoped_q=Lifetime If you have any doubts on the implementation of this, feel free to reach out to Mike (mdboom) :)
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Assignee: tlong → alessio.placitelli
Attached file GitHub Pull Request
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: