feat(site): show the verified rate per product alongside per record - #151
Merged
Conversation
Most smartphone records are regional and RAM variants of one phone, and no source documents an individual SKU, so the per-record figure reads lower than how well the products in the dataset are actually sourced. The homepage now shows both readings of the same verifications, the per-product one as a secondary line under the headline. The block removes itself when the snapshot predates the field rather than rendering a zero. Refs #1
github-actions
Bot
added
enhancement
Member
TechEngine change review: PASS
Changed data
Changed record examplessoc modified
smartphone modified
tablet modified
watch modified
pda modified
gpu modified
cpu modified
Heuristic review
Changed site
Modified site files
|
Member
TechEngine validation stats: PASS
Data summary
Warning Tracked verified coverage is below 50% for watch 4.2% (18/433), tablet 6.3% (218/3455), soc 6.9% (146/2104), brand 11.6% (24/207), smartphone 18.6% (17384/93396), all 20.0% (21114/105742), gpu 32.7% (663/2030), pda 47.1% (66/140). Validation notes
Key output:
Homepage build: |
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
2 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.
Homepage side of GetTechAPI/TechEngine#55.
Most smartphone records are regional and RAM variants of one phone (57,216 records stand for 20,594 models), and no source documents an individual SKU — so the per-record figure reads lower than how well the products in the dataset are actually sourced. Measured over the current smartphone data:
The verification panel now shows both readings of the same verifications, the per-product one as a secondary line under the headline. It reads
models/verified_models/verified_models_pctfrom the snapshot, whichbuild-verification.mjsalready passes through untouched — no build change needed.The block removes itself when the snapshot predates those fields rather than rendering a zero, so this is safe to merge before the engine side lands.
Refs #1
Closes #19