Route facts the simulator needs to build its 400 error: the host, the path,
and the method.
contentType is the content type of the route's success response, which
the generated code answers with; the simulated 400 is JSON whatever it is.
Evidence
contracts/common.md#principled-implementation The host, path, and method identify the request in the error, and the content type describes the success response of the generated function, which the generated code answers with.
Evidence
contracts/common.md#clear-and-simple-design A four-field record with no behavior.
Evidence
contracts/common.md#prohibited-implementation-shortcuts The values are supplied by the generated SDK for its own route.
Evidence
contracts/common.md#meaningful-documentation The comment says what each part is used for, with the contentType member documenting when it is null.
Content type of the route's success response, null for one without a
body such as HEAD's. The simulated 400 is JSON whatever it is, as the
server's is.
Route facts the simulator needs to build its 400 error: the host, the path, and the method.
contentTypeis the content type of the route's success response, which the generated code answers with; the simulated 400 is JSON whatever it is.Evidence
contracts/common.md#principled-implementation The host, path, and method identify the request in the error, and the content type describes the success response of the generated function, which the generated code answers with.
Evidence
contracts/common.md#clear-and-simple-design A four-field record with no behavior.
Evidence
contracts/common.md#prohibited-implementation-shortcuts The values are supplied by the generated SDK for its own route.
Evidence
contracts/common.md#meaningful-documentation The comment says what each part is used for, with the
contentTypemember documenting when it isnull.