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

--contractName and clause output are confusing #609

Closed
jeromesimeon opened this issue Apr 26, 2019 · 1 comment
Closed

--contractName and clause output are confusing #609

jeromesimeon opened this issue Apr 26, 2019 · 1 comment
Labels
Type: Bug 🐛 Something isn't working

Comments

@jeromesimeon
Copy link
Member

Since the latest release, ergorun expects a single top-level contract (similarly to Cicero), which makes --contractName useless and confusing.

Proof by example:

bash-3.2$ ./packages/ergo-cli/bin/ergorun.js execute ./examples/helloworld/model.cto ./examples/helloworld/logic.ergo --contractName nonsense --contract ./examples/helloworld/contract.json --request ./examples/helloworld/request.json --state ./examples/helloworld/state.json
12:25:12 - info:
{
  "clause": "nonsense",
  "request": {
    "$class": "org.accordproject.helloworld.Request",
    "input": "Accord Project",
    "transactionId": "58383c00-110f-44b4-8a22-2268b862dcad",
    "timestamp": "2019-04-26T16:25:12.804Z"
  },
  "response": {
    "$class": "org.accordproject.helloworld.Response",
    "output": "Hello Fred Blogs (Accord Project)",
    "transactionId": "965ee708-55ef-4a5a-9a38-80658e2bf538",
    "timestamp": "2019-04-26T16:25:12.817Z"
  },
  "state": {
    "$class": "org.accordproject.cicero.contract.AccordContractState",
    "stateId": "1"
  },
  "emit": []
}
@jeromesimeon jeromesimeon added the Type: Bug 🐛 Something isn't working label Apr 26, 2019
@jeromesimeon
Copy link
Member Author

Fixed in #611

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Bug 🐛 Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant