The idea of using predefined *.flows.js files from orchestration package in third party contracts is a work in progress.
Problem Solved
The current way orca contract demonstrates orchestration package is different to the flows approach described above. Here we take the first of step for unifying those approaches under one repository to have better teaching material for orchestration API.
What are some of the improvements flows brings and orca can use?
basic-flows.contract.js is bundled and deployed from the host machine using agoric run
basic-flows.contract.test.js uses commonSetup from the orchestration test environment to have simpler and more generic testing setup
Testing
I have confirmed that test pass and contracts can be deployed to multichain setup for both orca and flows.
What can be better?
Currently the folder structure is a little bit too nested. We should flatten that
Context
The idea of using predefined
*.flows.jsfiles fromorchestrationpackage in third party contracts is a work in progress.Problem Solved
The current way
orcacontract demonstratesorchestrationpackage is different to the flows approach described above. Here we take the first of step for unifying those approaches under one repository to have better teaching material fororchestrationAPI.What are some of the improvements
flowsbrings andorcacan use?basic-flows.contract.jsis bundled and deployed from the host machine usingagoric runbasic-flows.contract.test.jsusescommonSetupfrom the orchestration test environment to have simpler and more generic testing setupTesting
I have confirmed that test pass and contracts can be deployed to multichain setup for both
orcaandflows.What can be better?
Currently the folder structure is a little bit too nested. We should flatten that
cc @Jovonni