Skip to content
This repository has been archived by the owner on Jan 31, 2023. It is now read-only.

Instantiate requires a function name, otherwise defaults to "init" #587

Closed
sstone1 opened this issue Feb 13, 2019 · 0 comments
Closed

Instantiate requires a function name, otherwise defaults to "init" #587

sstone1 opened this issue Feb 13, 2019 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@sstone1
Copy link
Contributor

sstone1 commented Feb 13, 2019

The function name specified at instantiate time should be optional. You should not have to develop a function to be called at instantiate time, nor should you have to call any function at instantiate time. The new programming model enables this.

Unfortunately the Fabric SDK defaults to "init" when you pass in no function name, which causes errors when you don't have an "init" function.

Fortunately the Fabric SDK has now been fixed to stop defaulting to "init" when no function name is passed in, so we need to pick up the new SDK level that contains the fix.

@sstone1 sstone1 added the bug Something isn't working label Feb 13, 2019
@sstone1 sstone1 self-assigned this Feb 13, 2019
sstone1 pushed a commit to sstone1/blockchain-vscode-extension that referenced this issue Feb 13, 2019
Signed-off-by: Simon Stone <sstone1@uk.ibm.com>
@cazfletch cazfletch added this to the Sprint 1 milestone Feb 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants