-
Notifications
You must be signed in to change notification settings - Fork 20
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
try to fix #106 #108
try to fix #106 #108
Conversation
de5fd6b
to
10ccfcd
Compare
10ccfcd
to
61f2356
Compare
@bestbeforetoday , if there no further comments for this PR, I would like to merge it early next week. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestions for simplifying the API and usage in comments to consider.
I would also suggest only exporting a minimal set of functions. Several of the functions in signaturepolicy.go are capitalized and so are public. I'm not sure any of them need to be. Perhaps keep the public API to a single function until there is a clear need for more.
Signed-off-by: Sam Yuan <[email protected]>
61f2356
to
5c76227
Compare
Signed-off-by: Sam Yuan <[email protected]>
Signed-off-by: Sam Yuan <[email protected]>
Signed-off-by: Sam Yuan <[email protected]>
I suppose we need to provide function to support approve sign for chaincode level and channel level.
this PR is just a draft as POC.