Open davidyuk opened 2 years ago
For example, /compile accepts a Contract that defined as:
/compile
Contract
"Contract": { "properties": { "code": { "type": "string" }, "options": { "$ref": "#/definitions/CompileOpts" } }, "required": [ "code", "options" ], "type": "object" }, "CompileOpts": { "properties": { "backend": { "description": "Compiler backend; fate | aevm", "enum": [ "fate", "aevm" ], "type": "string" }, "file_system": { "description": "An explicit file system, mapping file names to file content", "properties": { }, "type": "object" }, "src_file": { "description": "Name of contract source file - only used in error messages", "type": "string" } }, "type": "object" },
can we inline options to have Contract looking like below?
"Contract": { "properties": { "code": { "type": "string" }, "backend": { "description": "Compiler backend; fate | aevm", "enum": [ "fate", "aevm" ], "type": "string" }, "file_system": { "description": "An explicit file system, mapping file names to file content", "properties": {}, "type": "object" }, "src_file": { "description": "Name of contract source file - only used in error messages", "type": "string" } }, "required": [ "code" ], "type": "object" },
For example,
/compile
accepts aContract
that defined as:can we inline options to have
Contract
looking like below?