forked from TrueCloudLab/neoneo-go
cbf26f315c
VM types are used in debugger, while smartcontract ones are used in manifest. We can't save only one of them, because conversion in either side is lossy: 1. VM has `Array` and `Struct` but smartcontract only has `Array`. 2. Smartcontract has `Hash160` etc, which are all `ByteString` or `Buffer` in VM. And to spice things a bit more, return type in debugger can be `Void`, which corresponds to no real stackitem type (as it must exist).
23 lines
No EOL
432 B
YAML
23 lines
No EOL
432 B
YAML
name: "Event types example"
|
|
supportedstandards: []
|
|
events:
|
|
- name: SomeBytes
|
|
parameters:
|
|
- name: bytes
|
|
type: ByteArray
|
|
- name: SomeInteger
|
|
parameters:
|
|
- name: int
|
|
type: Integer
|
|
- name: SomeString
|
|
parameters:
|
|
- name: str
|
|
type: String
|
|
- name: SomeMap
|
|
parameters:
|
|
- name: m
|
|
type: Map
|
|
- name: SomeArray
|
|
parameters:
|
|
- name: a
|
|
type: Array |