PQA002 — Invalid adapter configuration¶
The adapter registration cannot be parsed, or it declares a value the generator does not accept.
The message carries the reason: the parser's own error with the offending line, or a named rejection such as an unsupported transport type.
Why the build refuses this¶
A half-read model generates a half-built adapter. The generator would emit Thing classes for the types it managed to read and silently skip the rest, so the missing half surfaces as compile errors in hand-written code rather than as a problem in the declaration.
A rejected value has no fallback. The generator cannot guess what an unknown transport or frame type is supposed to do, and picking a default would produce an adapter that connects in a way nobody declared.
How to fix it¶
Read the reason in the message first. A parser error names the line and column; an indentation slip or a tab character is the common cause, because the document is YAML and tabs are not valid indentation there.
For a rejected value, take the accepted set from the message and from reference/adapter-registration.schema.json. Validating the document against that schema in the editor catches this before the build does.
If you disagree with a report¶
Do not suppress it. A wrong report is a bug in the check — report it with the YAML that triggered it.