-
Notifications
You must be signed in to change notification settings - Fork 207
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
calling flows from flows and other support for 9796 #10024
Conversation
Deploying agoric-sdk with Cloudflare Pages
|
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 - please consider the Proxying
-> Proxy
name change
// Osmosis is one of the few chains with icqEnabled | ||
const osmosis = await orch.getChain('osmosis'); |
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.
omniflix
appears to have icq enabled, but that's not to suggest we should revert this change. osmosis
is preferable from my POV since it's integrated in multichain-testing
- starship doesn't yet support omniflix
.
@@ -43,7 +43,7 @@ const preparePortfolioHolderKit = (zone, { asVow, when }) => { | |||
'PortfolioHolderKit', | |||
{ | |||
invitationMakers: M.interface('InvitationMakers', { | |||
MakeInvitation: M.call( | |||
Proxying: M.call( |
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.
Wb Proxy
, verb, instead of a present participle?
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.
That was my first thought too but since Proxy is a global object I thought it would be confusing.
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 added some commits to enable mapping guest flows anywhere in the context object and updated a test accordingly.
refs: #9796
Description
#10023 started with a series of refactors and cleanup. This separates those into another PR to be reviewed more rapidly.
It also includes a new feature to orchestrateAll to ease calling flows from flows. Each flow is available on the context object under
flows
.Security Considerations
Every flow can call another flow. In the event a developer wants isolate between flows, they won't put them in the same
orchestrateAll
.Scaling Considerations
n/a
Documentation Considerations
none
Testing Considerations
new tests
Upgrade Considerations
not yet deployed