-
Notifications
You must be signed in to change notification settings - Fork 123
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
Bug 1658349 - Allow using the quantity metric type outside of Gecko #1198
Conversation
After #1200 I should probably drop the C# commit, but then it would have glean_parser create invalid metrics. |
Nah, it's fine to leave this in. No worries. |
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 generally solid. A couple of comments, below.
ad2f5d1
to
6354a8b
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.
r+. Let's not merge until somebody reviews the Swift part, though
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.
This requires documentation updates here: https://mozilla.github.io/glean/book/user/metrics/quantity.html
Please also add a changelog entry.
0313c59
to
b39ca7b
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.
Last couple of comments but then good to go.
Co-authored-by: Jan-Erik Rediger <[email protected]>
fcee843
to
c849b40
Compare
Glean changelog: * General * Allow using quantity metric type outside of Gecko ([mozilla#1198](mozilla/glean#1198)) * Update `glean_parser` to 1.28.5 * The `SUPERFLUOUS_NO_LINT` warning has been removed from the glinter. It likely did more harm than good, and makes it hard to make metrics.yaml files that pass across different versions of `glean_parser`. * Expired metrics will now produce a linter warning, `EXPIRED_METRIC`. * Expiry dates that are more than 730 days (~2 years) in the future will produce a linter warning, `EXPIRATION_DATE_TOO_FAR`. * Allow using the Quantity metric type outside of Gecko. * New parser configs `custom_is_expired` and `custom_validate_expires` added. These are both functions that take the expires value of the metric and return a bool. (See `Metric.is_expired` and `Metric.validate_expires`). These will allow FOG to provide custom validation for its version-based `expires` values. * Add a limit of 250 pending ping files. ([mozilla#1217](mozilla/glean#1217)). Note: This also gets rid of the 2 workarounds (removed code) in AppService thanks to upstream changes.
Glean changelog: * General * Allow using quantity metric type outside of Gecko ([mozilla#1198](mozilla/glean#1198)) * Update `glean_parser` to 1.28.5 * The `SUPERFLUOUS_NO_LINT` warning has been removed from the glinter. It likely did more harm than good, and makes it hard to make metrics.yaml files that pass across different versions of `glean_parser`. * Expired metrics will now produce a linter warning, `EXPIRED_METRIC`. * Expiry dates that are more than 730 days (~2 years) in the future will produce a linter warning, `EXPIRATION_DATE_TOO_FAR`. * Allow using the Quantity metric type outside of Gecko. * New parser configs `custom_is_expired` and `custom_validate_expires` added. These are both functions that take the expires value of the metric and return a bool. (See `Metric.is_expired` and `Metric.validate_expires`). These will allow FOG to provide custom validation for its version-based `expires` values. * Add a limit of 250 pending ping files. ([mozilla#1217](mozilla/glean#1217)). Note: This also gets rid of the 2 workarounds (removed code) in AppService thanks to upstream changes.
glean_parser PR: mozilla/glean_parser#225