37af2031bb
There are two ways of doing this: first one is to emit all notifications parameter data into rpcbindings configuration on compile time (event if the parameter has a simple type), and the second one is to fetch parameter type from the manifest on rpcbinding file generation if needed (we always have manifest at this stage, thus it's not a problem to retrieve necessary information). The latter case is chosen to reduce the bindings configuration file size. Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru> |
||
---|---|---|
.. | ||
deploy | ||
gas | ||
invalid1 | ||
invalid2 | ||
invalid3 | ||
invalid4 | ||
nameservice | ||
nex | ||
nonepiter | ||
notifications | ||
structs | ||
types | ||
verifyrpc | ||
verify.go | ||
verify.manifest.json | ||
verify.nef | ||
verify.yml |