Graduated from #64; condition-triggered, no action until the trigger.
HttpJsonBindingProtocol's identity (name, trait id, error-identity header, status fallback) rides as four positional constructor args today, with the error-header semantics documented separately on each generator half. That's fine with one caller (simpleRestJson()); the moment a second factory (e.g. a restJson1 flavor) is added, introduce a record HttpJsonProtocolIdentity(...) so the facts travel together and the constructor call sites stay readable. Doing it now would be speculative structure — this issue exists so the idea is findable at the right moment.
Graduated from #64; condition-triggered, no action until the trigger.
HttpJsonBindingProtocol's identity (name, trait id, error-identity header, status fallback) rides as four positional constructor args today, with the error-header semantics documented separately on each generator half. That's fine with one caller (simpleRestJson()); the moment a second factory (e.g. a restJson1 flavor) is added, introduce arecord HttpJsonProtocolIdentity(...)so the facts travel together and the constructor call sites stay readable. Doing it now would be speculative structure — this issue exists so the idea is findable at the right moment.