Summary or problem description
For example RpcClient method GetContractStateAsync doesn't even use its model class at all for serializing and deserializing .
RpcClient
RpcStateRootNoToJson
RpcMethodTokenNoToJson
RpcFoundStatesNoToJson
GetContractStateAsync
Possibly More
Do you have any solution you want to propose?
We have some kind of standard for writing plugins; code in general. For example, Folder structure layout. Maybe Interfaces for certain things like getting storage from other plugins. Making and writing unit tests. A naming convention for properties names in config.json. Just to name a couple. If we don't as you can see things can get lost in time, as new requirements come along and deadlines need to be met. Also we can update .editorconfig file for most of these little things.
Where in the software does this update applies to?
Summary or problem description For example RpcClient method
GetContractStateAsyncdoesn't even use its model class at all for serializing and deserializing .RpcClient
RpcStateRootNoToJsonRpcMethodTokenNoToJsonRpcFoundStatesNoToJsonGetContractStateAsyncDo you have any solution you want to propose? We have some kind of standard for writing plugins; code in general. For example, Folder structure layout. Maybe Interfaces for certain things like getting storage from other plugins. Making and writing unit tests. A naming convention for properties names in
config.json. Just to name a couple. If we don't as you can see things can get lost in time, as new requirements come along and deadlines need to be met. Also we can update.editorconfigfile for most of these little things.Where in the software does this update applies to?