Vitaly Bogdanov
Vitaly Bogdanov
There are few linters which can check Solidity code style. One can find their list at the end of the page: https://consensys.github.io/smart-contract-best-practices/security_tools/
singnet/snet-daemon#99 is closed so I am removing the FIXME banner in snet-daemon in `snet-daemon` sources https://github.com/singnet/snet-daemon/pull/446.
Looks like `orgName` in contract was replaced by `metadataURI` and since that some `snet-cli` functionality requires modification. See https://github.com/singnet/snet-cli/issues/348 as well.
@raamb , how category is different from tag?
We have discussed it with @astroseger today: - if client uses SDK then it can implement protocol which is described by publisher in protobuf comments and there is no protocol...
One of the options I see is to allow commenting `.proto` files using `Doxygen` or other documentation generator and adding separate `snet-cli` command to generate documentation for the service. I...
One possible way is to publish new github release each time when we need new version globally. It can be published manually for instance using some script. Or we can...
I have added first development release for platform-contracts manuall [release v0.2.2](https://github.com/singnet/platform-contracts/releases/tag/v0.2.2) Commands to create release tarball: ```sh VERSION=0.2.2 npm install npm run compile npm run package-npm cd build mv npm-module...
I would say we should automate release publishing first then we can close it.