Uh oh!
There was an error while loading. Please reload this page.
chore(spec): cut orphaned object.recordTypes and object.cdc stubs - #1960
Merged
Conversation
Both were spec-only properties with elaborate docstrings and zero consumers in either repo (framework runtime + objectui authoring/ rendering), classified `dead` in the liveness ledger: - `recordTypes`: a Salesforce-specific concept. The platform models record variants via a discriminator field + conditional layouts (visibleWhen / form variants), so this stub is redundant. - `cdc` / `CDCConfigSchema`: aspirational enterprise change-data- capture. Low-code change propagation is served by webhooks + triggers; no streaming runtime exists. Removes false surface from the metadata contract. Gate stays green (object 56 classified), spec tests 6562 passed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📓 Docs Drift CheckThis PR changes 1 package(s): 89 hand-written doc(s) reference the affected code and may need an implementation-accuracy re-verification:
|
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Removes two spec-only properties from
ObjectSchemathat had elaborate docstrings but zero consumers in either repo (framework runtime + objectui authoring/rendering). Both were classifieddeadin the spec-liveness ledger.object.recordTypesvisibleWhen/ form variants)object.cdc(+CDCConfigSchema,CDCConfigtype)This is part of the spec-liveness "narrow-and-true" hygiene: shedding false surface from the metadata contract. Verified orphaned in both
frameworkand../objectuibefore removal (cross-repo grep + read).Verification
check:livenessgreen —object 56 classified, all governed properties classified.gen:schemaregenerates clean (1686 schemas).@objectstack/spectests: 6562 passed (242 files).recordTypes/CDCConfigreferences remain anywhere underpackages/(excludingdist/node_modules).🤖 Generated with Claude Code