findUndeliverableBinaryFormatIssues
findUndeliverableBinaryFormatIssues(
raw):DeprecatedConfigIssue[]
Defined in: packages/core/src/config/schema.ts:2311
CFG-68 — every binaryFormats entry naming a format type no provider can receive, found on the
RAW input, with the path that names the offending entry. CFG-74 — and every entry whose type
is missing or not a string, at the same path, for the same reason.
The half that is load-bearing is the missing/non-string one, and it is load-bearing because
the enum’s own sentence argues about a value the user never wrote. The enum’s error hook renders
issue.input, so an entry with no type at all is refused as undefined is not a binary format type — a sentence about a value, for an entry that has none. These two shapes get a sentence
naming the SHAPE instead (malformedBinaryFormatTypeMessage), and because the scan runs
BEFORE the parse — exactly as findApprovalsGrammarIssues arranges for its own — that is
the only sentence the user reads.
The undeliverable-VALUE half says what the parse now says on its own, in the same words — both routes render undeliverableBinaryFormatMessage, which is why one function owns that sentence — and is kept so the vocabulary is refused on the RAW input, before any arm of the union is tried.
Only type is scanned. An entry’s other fields, and an entry that is not an object, fall
through to the union, whose arms formatConfigValidationError descends into — so those
report at their own path too, in zod’s words rather than in ours.
PURE: it only reads the object.
Parameters
Section titled “Parameters”Record<string, unknown>