Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
The idea of using predefined
*.flows.js
files fromorchestration
package in third party contracts is a work in progress.Problem Solved
The current way
orca
contract demonstratesorchestration
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 fororchestration
API.What are some of the improvements
flows
brings andorca
can use?basic-flows.contract.js
is bundled and deployed from the host machine usingagoric run
basic-flows.contract.test.js
usescommonSetup
from 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
orca
andflows
.What can be better?
Currently the folder structure is a little bit too nested. We should flatten that
cc @Jovonni