Skip to content
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

Merged
merged 7 commits into from
Dec 20, 2023
Merged

Update getting started guide #202

merged 7 commits into from
Dec 20, 2023

Conversation

cam-schultz
Copy link
Contributor

Why this should be merged

Updates the Getting Started Guide to reflect the latest version of ExampleCrossChainMessenger, which uses TeleporterOwnerUpgradeable, 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 with TeleporterMessenger to doing so indirectly through TeleporterRegistry.

How this works

N/A

How this was tested

N/A

How is this documented

Self explanatory

@cam-schultz cam-schultz added the documentation Improvements or additions to documentation label Dec 14, 2023
@cam-schultz cam-schultz self-assigned this Dec 14, 2023
geoff-vball
geoff-vball previously approved these changes Dec 14, 2023
Copy link
Contributor

@bernard-avalabs bernard-avalabs left a 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.

contracts/src/CrossChainApplications/GETTING_STARTED.md Outdated Show resolved Hide resolved
geoff-vball
geoff-vball previously approved these changes Dec 19, 2023
Copy link
Collaborator

@michaelkaplan13 michaelkaplan13 left a 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
Copy link
Collaborator

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:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:

Copy link
Contributor Author

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.

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 "../../"?

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

Copy link
Contributor Author

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.

geoff-vball
geoff-vball previously approved these changes Dec 20, 2023
@cam-schultz cam-schultz merged commit 83ee0af into main Dec 20, 2023
15 checks passed
@cam-schultz cam-schultz deleted the update-getting-started branch December 20, 2023 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants