Skip to content

Conversation

@tanfarming
Copy link
Contributor

@tanfarming tanfarming commented Dec 17, 2025

@tanfarming tanfarming requested a review from a team as a code owner December 17, 2025 15:58
@tanfarming tanfarming merged commit 3cad719 into main Jan 9, 2026
2 checks passed
@tanfarming tanfarming deleted the geng/ae1120 branch January 9, 2026 15:02
Comment on lines 317 to 318
Version of the Firefox browser being used by the client. Used for error investigation only, no
analytics value.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Used for error investigation only, no analytics value.

this phrase feels kind of meaningless -- if we populate the field in the table then it can be queried, and then there will be things with a dependency on it. I get that this phrasing was used because it's the same one that some of our other metrics have, but I kind of feel like we should remove it.

Once a field exists in a glean table, there's no sentiment-based restriction that exists when querying it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants