-
Notifications
You must be signed in to change notification settings - Fork 206
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
remove orch.makeLocalAccount
#10260
remove orch.makeLocalAccount
#10260
Conversation
6f6ec04
to
17a1001
Compare
Deploying agoric-sdk with Cloudflare Pages
|
17a1001
to
fb69394
Compare
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 take the fact that no tests fail without it as evidence it isn't necessary for any use cases of the product
* chainHub: ChainHub; | ||
* localchain: Remote<LocalChain>; | ||
* makeRecorderKit: MakeRecorderKit; |
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 expect some of these will need to be restored later but I agree it's better to leave them out until they're used
b6e0883
to
3356749
Compare
3356749
to
fa13c4e
Compare
closes: #10106
Description
There doesn't seem to be a motivating use case for exposing a maker for a low-level
LocalChainAccount
in theOrchestrator
, so lets remove it to avoid misdirection. Instead, consumers can callorch.getChain('agoric').then(c => c.makeAccount())
to get aLocalOrchestrationAccount
.Security Considerations
n/a
Scaling Considerations
n/a
Documentation Considerations
docs.agoric.com already reflects this: Agoric/documentation#1208 (comment)
Testing Considerations
Removing code, so existing tests suffice
Upgrade Considerations
Library code that will go out in a NPM Orch Release