next/font: tolerate missing unused fields in capsize map #50708
Merged
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.
Some font entries in capsize do not include fields like
cap_height
andx_height
. Since these are unused by next/font, remove these from the serde structure entirely.Additionally, this makes it so that failing to read or deserialize the capsize map results in an
Error
rather than aFontFallbackError
, which causes a build failure rather than silently omitting a fallback font.next/font
should always include this map, and it obscured the real issue here. However, a missing entry in this map should result in omitting a fallback.