Request Body Objects
Source
val insert_request_body :
Json_query.path ->
OaTypes.request_body ->
OaTypes.request_body DkStdRestApis_Gen.OaTypes.Request_body_map.t ->
OaTypes.request_body DkStdRestApis_Gen.OaTypes.Request_body_map.tSource
val insert_op_request_body :
Json_query.path ->
OaTypes.operation_id ->
OaTypes.request_body ->
OaTypes.request_body DkStdRestApis_Gen.OaTypes.Operation_request_body_map.t ->
OaTypes.request_body DkStdRestApis_Gen.OaTypes.Operation_request_body_map.tSource
val request_body_exists :
Json_query.path ->
'a DkStdRestApis_Gen.OaTypes.Request_body_map.t ->
boolinclude DkCoder_Std.SCRIPT
__init context is the entry point for running a script module. The DkCoder compiler will inject this function at the top and bottom of the script module. The top __init does nothing, while the bottom __init calls the prior __init.
That means:
- calling the
__initfunction guarantees that the script module is initialized; that is, all of the script module's side-effects (ex.let () = Format.printf "Hello world@.") are executed before the__initreturns to the caller. - you can override the
__initfunction by simply defining the__initidempotently. That will shadow the top__initand when the bottom__initis executed your__initwill be called instead of the do-nothing top__init.
Future versions of DkCoder will call __init in dependency order for all `You script modules. Your __init function may be called several times.
__repl context is the entry point for debugging a script module in a REPL. The DkCoder compiler will inject this function at the top and bottom of the script module. The top __repl does nothing, while the bottom __repl calls the prior __repl.
That means:
- you can override the
__replfunction by simply defining the__replidempotently. That will shadow the top__repland when the bottom__replis executed your__replwill be called instead of the do-nothing top__repl.
The run-time module information for the script module.
