chore(metadata): clear the dead-metadata findings of os validate --strict - #1983
Merged
Merged
Conversation
…rict - views: nine rowColor maps wrote hex colours, which the console resolves to nothing; write the matching colour names so the documented row tints actually draw. - dashboards: drop 84 widget `options` keys no renderer reads (icons, formats, table columns/striped/density, suffix, pivot field keys). Every removed format matched its measure's own. - permission sets: move four rowLevelSecurity label/description values (liveness: dead) into comments. os validate --strict: 111 -> 16 warnings. The 16 left are deliberate and listed in the changeset (enterprise capability, position-routed approvals, template expressions, two test-pinned keys, one ruling-pinned card description). Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WXp8E7s1gzSBje9ZwwqVux
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Neither key reaches a renderer (`unconsumed-widget-option`): the pivot never opened a drill-down drawer and the SLA gauge never drew the green/amber/red bands. Remove both, with the test assertions that pinned them: the drill-down column check in ownership-model (it would run over nothing) and the threshold-band assertions in sla-compliance-gauge. The gauge keeps its pins on the compliance measure, its computed value and the 0.95 target line. os validate --strict: 16 -> 14 warnings, all deliberate. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WXp8E7s1gzSBje9ZwwqVux
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.
Description
This is the follow-up promised in #1982. On 17.6.0,
os validate --strictreports 111 warnings. This PR clears 97 of them, all of which are metadata the platform never read. The 14 left are deliberate, and each is listed below with its reason.--strictis not part ofpnpm verify, and this PR does not add it.Type of Change
Related Issues
Related to #1982 (the 17.6.0 upgrade; its PR body lists these findings as a follow-up).
Changes Made
rowColormaps use colour names instead of hex (src/*/views/*.view.ts). objectui'suseRowColorresolves only a name from its own vocabulary or a fullbg-*class, and a hex value resolves to no colour at all. So until now no row was ever tinted, althoughcontent/docs/service/cases.mdxandcontent/docs/sales/opportunities.mdxsay rows are tinted. Each hex maps to the matching Tailwind family; the renderer draws the-100shade.list, which the All Accounts landing tab does not use, so that tab is unchanged.optionskeys are deleted across the activity, CRM, sales and service dashboards andshared-widgets.ts.icon/format, tablecolumns/striped/density, asuffix, the pivot's field keys and itsdrillDown, and the SLA gauge'sthresholds.unconsumed-widget-optionreports that no renderer reads them. A dataset-bound widget takes its labels and formats from the dataset.formatwith the format of the measure it displays. They match, or the measure is a plain count. The dashboards do not change. The pivot never opened a drill-down drawer, and the gauge never drew the green/amber/red bands.test/ownership-model.test.tsdrops "dashboard drill-down column lists name real record columns". With no drill-down left, it would run over nothing.test/sla-compliance-gauge.test.tsdrops its threshold-band assertions, including the "lands in the success band" test, which read only the ladder.colorVariant, the absence ofinvert, and the 0.95 target line.rowLevelSecurity[]label/descriptionvalues move into comments, in thesales_managerandmarketing_userpermission sets. These keys areliveness: dead.Still reported (14), on purpose
hierarchy-securitycapability is enterprise-only{…}template expression (could be a CEL envelope)page:carddescriptionon Sales Hometest/metadata-references.test.ts).Testing
pnpm verifygreen: validate, typecheck, lint, i18n gate, hygiene, build, and 3723 tests. Of the 3725 tests before this PR, the 2 removed are the threshold and drill-down tests above.os validate --strict: 111 → 14 warnings, exactly the set listed above.🤖 Generated with Claude Code
https://claude.ai/code/session_01WXp8E7s1gzSBje9ZwwqVux