-
Notifications
You must be signed in to change notification settings - Fork 333
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: fix Token Bridge tutorial #10638
Comments
As an alternative, we could set up a test file, specifically designed to be used only with published npm packages. It could use these helper functions from aztec.js The test file would:
The tutorial would grab sections of this test file. |
Trying out a simple script here: https://github.com/critesjosh/token-bridge-tutorial-test/blob/0.66/index.ts blocked by getting |
I'm taking this @critesjosh |
This PR updates the token bridge tutorial pages in the docs, and adds an e2e test to ensure that referenced code is always working. closes #10638
The token bridge tutorial does not currently work.
As it's currently designed, the tests rely on many files:
The tutorial broke because many of these files changed recently. I am starting to think it would easier to have people to clone the monorepo and list commands in the tutorial to copy files directly out of the monorepo into their project rather than have them copy+paste large code blocks. If we set up a foundry project and list aztec-packages as a dependency, it will clone it into
lib/
when runningforge install
. A drawback of this approach is that devs need to have forge installed (may not be a big issue).Adding these to
foundry.toml
enables theTokenPortal.sol
as its written to compile (even though it's not strictly necessary for the tutorial tests to run).The text was updated successfully, but these errors were encountered: