-
Notifications
You must be signed in to change notification settings - Fork 27
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
Update getting started guide #202
Conversation
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.
Generally looks good to me. Added a comment regarding active/passive voice.
Co-authored-by: Michael Kaplan <[email protected]> Signed-off-by: cam-schultz <[email protected]>
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.
👍
|
||
To start, replace the import for `ITeleporterReceiver` with `TeleporterOwnerUpgradeable`: | ||
|
||
```diff |
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 know you could put diffs in READMEs like this. Very nice!
{} | ||
``` | ||
|
||
Finally, add the following struct and event declarations to the contract, which will be integrated in later: |
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.
Finally, add the following struct and event declarations to the contract, which will be integrated in later: | |
Add the following struct and event declarations to the contract, which will be integrated in later: |
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.
Gonna keep this as is to match the flow of the rest of this step.
@@ -4,31 +4,70 @@ This section walks through how to build an example cross-chain application on to | |||
|
|||
## Step 1: Create Initial Contract | |||
|
|||
Create a new file called `MyExampleCrossChainMessenger.sol` in the directory that will hold the application. | |||
Create a new file called `MyExampleCrossChainMessenger.sol` in a `teleporter/contracts/src/CrossChainApplications/MyExampleCrossChainMessenger/` directory. |
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.
Are you clarifying the exact path because of the imports with "../../"?
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.
Can you separate and add a line to create a new directory MyExampleCrossChainMessenger
at the path, then create file under that directory
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.
Not sure what you mean by exact path. The remappings don't apply to bash commands. We should circle back and add those remappings to these contracts, but I'm not going to do that in this PR.
Added exact commands as requested.
…er into update-getting-started
dcde08c
Why this should be merged
Updates the Getting Started Guide to reflect the latest version of
ExampleCrossChainMessenger
, which usesTeleporterOwnerUpgradeable
, as well as a handful of other changes that fell through the cracks. Also adds a standalone Upgrades section, demonstrating how to modify the contract from directly interacting withTeleporterMessenger
to doing so indirectly throughTeleporterRegistry
.How this works
N/A
How this was tested
N/A
How is this documented
Self explanatory