New features in Core v0.7
Advance data definition in service definition
Service’s definition now accept 3 new ways to describe the service’s data.
Array
We introduce the parameter repeated to specify arrays.
Each element of the array has the type define with the parameter type.
tasks:
list:
outputs:
success:
data:
addresses:
type: String
repeated: true
{
"addresses": ["string1", "string2", "string3"]
}
Nested Object
Object definition can now be a lot more precise with the introduction of the parameter object.
object parameter accept a map of keys / parameters.
tasks:
sign:
inputs:
transaction:
type: Object
object:
nonce:
type: Number
to:
type: String
value:
type: Number
gasLimit:
type: Number
gasPrice:
type: Number
{
"transaction": {
"nonce": 1,
"to": "0x1",
"value": 1000000000,
"gasLimit": 1000000,
"gasPrice": 21000000
}
}
Any
The type Any has been added to accept any type of data. No verification is done when using this type.
tasks:
exec:
inputs:
data:
type: Any
More info in the docs: https://docs.mesg.com/guide/service/service-file.html
For the complete changelog, refer to Github .
To update to v0.7, follow the installation process on the documentation