-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Completely Remove Short Name Support #390
Completely Remove Short Name Support #390
Conversation
035d769
to
2eaa1cc
Compare
2eaa1cc
to
11ba10b
Compare
904f273
to
86eea66
Compare
I was playing around with the error text,a nd I realized that the defaults are still set in the main
I would remove those from that script, and then set the defaults to "NA" in the first lines of the deployCC script. You can then set the following if statements accordingly |
@nikhil550 I noticed that when I was playing with the script but couldn't figure out why it was still setting them to the defaults. Thanks for pointing that out. |
Actually, playing around, removing them is the wrong thing to do. If you remove the defaults, then the variables do not exist. Rather, set them to NA in the network.sh script instead. |
Would we still need to check if the variables are empty then in the deployCC script, since our variables will now always be set to NA by default? |
You can check for "NA". see comment above. |
86eea66
to
f813b96
Compare
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.
I grepped fabric-samples and fabric for occurrences of "deployCC". I see a few more occurrences where not all three flags are provided (ccn, ccp, ccl).
49fcf4f
to
7cf5fad
Compare
test-network/scripts/deployCC.sh
Outdated
elif [ ! -d "$CC_SRC_PATH" ]; then | ||
fatalln "Path to chaincode does not exist. Please provide different path" | ||
fatalln "Path to chaincode does not exist. Please provide different path. ./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-go -ccl go" |
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.
You can probably remove the valid call example from this message. (If you keep it, add the text Valid call example:
Looks good, just a couple nits. You will need to update the help text to state that go is no longer he default chaincode language:
|
Signed-off-by: Julian Castrence <juliancastrence@ibm.com>
7cf5fad
to
12f7f29
Compare
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.
LGTM. I will leave open in case anyone else has any comments
Hi guys, Please correct me for any mis understanding. Short names are a crutch that can prevent someone from learning how to deploy their own chaincode. Short names have been replaced with their full path name. Short names are no longer recognized by shell scripts. but ... why removed the default values? |
Signed-off-by: SamYuan1990 <yy19902439@126.com>
Signed-off-by: SamYuan1990 <yy19902439@126.com>
Signed-off-by: SamYuan1990 <yy19902439@126.com>
Type of change
Description