feat(devices): add release years to presets - #12
Merged
Merged
Conversation
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
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.
What does this PR do?
Bundled device profiles now include a required
releaseYear, so device selectors can sort the 171 included profiles chronologically without handling a missing value. CustomDeviceProfilevalues remain compatible without a year.Each year is stored beside its profile in the platform table. The table test catches any preset without a valid year. Names that intentionally combine multiple model generations use the earliest represented release year for deterministic sorting. The device coverage tables now include recognizable model names, including separate inner and outer profiles for HUAWEI Mate X6.
The three platform tables are formatted with Oxfmt. Its JSONC config uses trailing commas for multi-line structures. Oxlint runs alongside the existing ESLint rules, and CI checks the Oxfmt output before building.
How was this verified?
pnpm format:checkpnpm buildpnpm testpnpm lintpnpm check-typesChecklist
pnpm lintpasses with zero warningsCHANGELOG.mdupdated under## [Unreleased]