Many users raise questions on how to test chaincode. It used
to be much easier with the old shim, as they could directly
use the old mock stub in the shim. Now that it no longer exists
the fabcar example can provide an example of how to test chaincode.
Also worth noting is our current directory structure of our Go
chaincodes prevents the creation of mocks due to import cycles.
This change also pushes the chaincode logic down into a `contract`
package.
Signed-off-by: Brett Logan <brett.t.logan@ibm.com>
The ccenv used to build Go chaincode is being
updated to no longer include the shim
dependency. Go chaincode must now vendor
all of its dependencies prior to being
packaged and installed.
Go chaincodes have been updated to include
go.mod for versioned dependencies.
Change-Id: Ib971cd3f841d5c92a509450bd85f6e424cc60c6e
Signed-off-by: Gari Singh <gari.r.singh@gmail.com>
