Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NWO: Go chaincode packager needs a new implementation #378

Open
davidkel opened this issue Aug 26, 2022 · 0 comments
Open

NWO: Go chaincode packager needs a new implementation #378

davidkel opened this issue Aug 26, 2022 · 0 comments
Labels
enhancement New feature or request NWO All about our testing infrastructure testing All related to testing

Comments

@davidkel
Copy link
Contributor

The current NWO chaincode packager currently packages the whole of fabric-smart-client and then relies on fabric to reference the chaincode stored inside the source code tree.

This isn't really optimal and also means that some hardcoded checks are made against the path to address being able to locate the code.

A new implementation should be provided at first to exist along side the current implementation (to allow for easy transition for fabric-token-sdk) that only packages the chaincode itself and is flexible enough to not require hardcoded paths, GOPATH to be set or even a path declared as a module name. It should be either an absolute path that the caller can compute (not hardcoded) to ensure maximum flexibility for fabric-smart-client, fabric-token-sdk and also allow consumers of these toolkits to be able to utilise NWO themselves

@mbrandenburger mbrandenburger added enhancement New feature or request testing All related to testing NWO All about our testing infrastructure labels Aug 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request NWO All about our testing infrastructure testing All related to testing
Projects
None yet
Development

No branches or pull requests

2 participants