validateBindings
Call Signature
Section titled “Call Signature”validateBindings(
scan,triggers?):BindingIssue[]
Defined in: packages/simply-aep-core/src/at4dxValidate.ts:384
Validate a scan’s AT4DX Application Factory binding records for wiring problems resolveBindings/
list don’t fail on: a binding with no resolvable key, a Selector/Domain/UnitOfWork binding whose
SObject reference is ambiguous or names an object EntityDefinition can’t actually reference, two
Service/Selector/Domain records sharing a platform-unique To__c, two Domain (or two UnitOfWork)
records resolving to the same SObject, two UnitOfWork records sharing a BindingSequence__c, and the
same DeveloperName defined more than once within one binding type.
See docs/design/0015-at4dx-binding-validate-create-set.md for the original rationale behind each rule,
and docs/design/0017-at4dx-binding-unit-of-work-write-support.md for why UnitOfWork was brought into
every rule here except duplicate-to (it has no To__c field, permanently).
Parameters
Section titled “Parameters”Pick<LocalScanResult, "records" | "malformed" | "ambiguous">
triggers?
Section titled “triggers?”Apex triggers scanned via scanLocalApexTriggers/scanOrgApexTriggers, for missing-domain-trigger. Omitted entirely (in either call form) skips that one rule — every other rule is unaffected.
Returns
Section titled “Returns”One issue per problem found. Empty when nothing’s wrong.
Call Signature
Section titled “Call Signature”validateBindings(
records,diagnostics,triggers?):BindingIssue[]
Defined in: packages/simply-aep-core/src/at4dxValidate.ts:388
Validate a scan’s AT4DX Application Factory binding records for wiring problems resolveBindings/
list don’t fail on: a binding with no resolvable key, a Selector/Domain/UnitOfWork binding whose
SObject reference is ambiguous or names an object EntityDefinition can’t actually reference, two
Service/Selector/Domain records sharing a platform-unique To__c, two Domain (or two UnitOfWork)
records resolving to the same SObject, two UnitOfWork records sharing a BindingSequence__c, and the
same DeveloperName defined more than once within one binding type.
See docs/design/0015-at4dx-binding-validate-create-set.md for the original rationale behind each rule,
and docs/design/0017-at4dx-binding-unit-of-work-write-support.md for why UnitOfWork was brought into
every rule here except duplicate-to (it has no To__c field, permanently).
Parameters
Section titled “Parameters”records
Section titled “records”diagnostics
Section titled “diagnostics”The malformed/ambiguous records the same scan reported alongside records. Omitted when the first argument is already a scan envelope.
ambiguous
Section titled “ambiguous”malformed
Section titled “malformed”triggers?
Section titled “triggers?”Apex triggers scanned via scanLocalApexTriggers/scanOrgApexTriggers, for missing-domain-trigger. Omitted entirely (in either call form) skips that one rule — every other rule is unaffected.
Returns
Section titled “Returns”One issue per problem found. Empty when nothing’s wrong.