Closed SamYuan1990 closed 1 year ago
if we want to replace fabric cli, we'd better create a cmd package and put implementation there?
There is already a hyperledger/fabric-cli project. It's currently based on the legacy Go SDK. If the CLI there looks good, perhaps we could rework that project and base it on this admin SDK. It might be a good discussion to have on a Fabric contributor call.
if we want to replace fabric cli, we'd better create a cmd package and put implementation there?
There is already a hyperledger/fabric-cli project. It's currently based on the legacy Go SDK. If the CLI there looks good, perhaps we could rework that project and base it on this admin SDK. It might be a good discussion to have on a Fabric contributor call.
en, maybe we can ask them to switch to our package to avoid duplication works?
Currently for packages tools it mostly used by test package. Hence remove function from tools to test package, and remove package tools as refactor. in further if we want to replace fabric cli, we'd better create a cmd package and put implementation there?