-
Notifications
You must be signed in to change notification settings - Fork 586
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: adding site docs for 09-localhost client #3147
Conversation
Feel free to make any suggestions and/or push to this branch 🙌 |
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.
Thanks for starting this @damiannolan ! I have some suggestions in terms of the narrative:
- I can imagine the use cases of the localhost client/connection is not trivially clear, so it would make sense to me to add some more explanation. Question is whether we elaborate here or write a complementary product focused blog post and link to it here...
- Given the localhost client has some differences at the transport layer (while attempting to preserve application level interface afaiu), I think it'd be good to list all of these differences in the overview. I was thinking of a table format even, comparing localhost and a 'regular' client (not localhost or solomachine). The differences are discussed throughout the docs but I think it would be nice to have an overview table
I can take a stab at this
There's some notes about use cases in the requirements doc in #3120 but yeah, either adding something here or in a blogpost would be good too for visibility. |
I've made the following changes:
Please check if I got all of it in the table... |
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.
Thank you for starting this work!! I left various comments, but overall looks good to me!
| Number of connection(s) | many connections, 1 (or more) per client | single sentinel `ConnectionEnd` representing a connection | | ||
| Connection creation | connection handshake, provided underlying client | the `ConnectionEnd` is created and set in store via the `InitGenesis` handler of the 03-connection submodule in core IBC | | ||
| Counterparty | underlying client, representing another chain | `09-localhost` | | ||
| Channel creation | channel handshake, provided underlying connection | channel handshake, **out of the box** | |
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.
What does this mean? It seems a bit "hype" to me. "out of the box" isn't very impressive in this situation since it's just talking about a connection existing. It takes less than 30 seconds to initiate a connection using "regular clients". I think I'd prefer to minimize the amount of information that has to be read and assume the reader is able to deduce that channels can be immediately created using the sentinel localhost connection
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've removed the "Channel Creation" row as channels are more or less treated the same
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.
Didn't intend to be claiming it was an 'impressive' feat by any means :) My thinking here was "what does all of this mean if I'm a dev who wants to start testing with localhost when used to a setup having 2 chains"? And then the only thing changing really from that POV is that I can immediately create my channel vs first having to create client and connection... so more pragmatic than hype
Sure the reader could deduct it, but that holds for everything in the table. I personally just like when I can quickly gather all info from an overview table when I need a quick reminder
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 makes sense. Apologies if my comment seemed strong, that wasn't the intention. I'm just looking to make sure the language remains neutral.
I have no preference if we keep this section but maybe we could use the wording "channel handshake on top of existing connection end connection-localhost
" or something like that
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.
no worries, I learned now you don't like hype trains lol 🚂
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.
Thank a lot for this, @damiannolan
Co-authored-by: Carlos Rodriguez <carlos@interchain.io> Co-authored-by: colin axnér <25233464+colin-axner@users.noreply.github.com>
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! Thanks for all the work with these docs ❤️
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, thanks for finishing this up!
Co-authored-by: tmsdkeys <98807841+tmsdkeys@users.noreply.github.com>
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.
Great work! Many thanks to everyone who spent time on this! :)
Description
closes: #3055
Commit Message / Changelog Entry
docs: adding site docs for 09-localhost client
see the guidelines for commit messages. (view raw markdown for examples)
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
) or specification (x/<module>/spec/
).godoc
comments.Files changed
in the Github PR explorer.Codecov Report
in the comment section below once CI passes.