Core: Align content stats fields with latest Spec changes#16439
Merged
Conversation
nastra
force-pushed
the
content-stats-align-impl
branch
3 times, most recently
from
355684d to
51be71e
Compare
wombatu-kun
reviewed
Jun 5, 2026
nastra
force-pushed
the
content-stats-align-impl
branch
from
51be71e to
7165fb6
Compare
nastra
force-pushed
the
content-stats-align-impl
branch
from
7165fb6 to
88bd2ac
Compare
danielcweeks
approved these changes
Jun 8, 2026
danielcweeks
left a comment
danielcweeks
left a comment
Contributor
There was a problem hiding this comment.
Verified all the updated ids/mappings per the spec. Looks good to me.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This aligns the different content stats field with the latest spec changes that were introduced by #14234. It also updates how the content stats schema is generated for Geo & Variant.
This PR doesn't cover the updated calculations for the two reserved metadata fields and will be handled in a separate PR.
The PR was created with the help of Claude Opus 4.7 and manually adjusted in a few places.