-
Notifications
You must be signed in to change notification settings - Fork 39
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
docs: initial docs for chainhub #1142
Conversation
Deploying documentation with Cloudflare Pages
|
Cloudflare deployment logs are available here |
d418451
to
071fea6
Compare
|
||
The core functionality is encapsulated within the `makeChainHub` function, which sets up a new `ChainHub` in the given zone. The `ChainHub` is responsible for: | ||
|
||
## **chainHub.registerChain(name, chainInfo)** |
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.
Either remove chainHub
in all APIs or add to all of them.
I think for cleaner presentation you may just delete chainHub
in all.
Also, because this is a heading, you may also delete the parameters. But I haven't seen at other pages to confirm what is the convention here.
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.
Adding chainHub
with all APIs. Followed conventions from here
6abeb9c
to
d8056fe
Compare
chore: revert index.js and yarn.lock to older versions
d8056fe
to
f2f4dd7
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.
This looks like reference docs.
Let's please get it in @agoric/orchestration reference docs instead, please.
The PR documents ChainHub API with code examples.
rendered:
refs