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.

Sign up for GitHub

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

fix: docs fixtures outdated #156

Merged
merged 1 commit into from
Nov 16, 2024
Merged

fix: docs fixtures outdated #156

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/source/core_concepts/named_contracts.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
Named Contracts
###################

One of the major differentiators between moccasin and other smart contract development tools is more flexible and powerful scripting. One of the such cabailities is built in :doc:`fixtures </core_concepts/testing/fixtures>` and :doc:`named contracts </core_concepts/named_contracts>`.
One of the major differentiators between moccasin and other smart contract development tools is more flexible and powerful scripting. One of the such cabailities :doc:`named contracts </core_concepts/named_contracts>`.

**Named contracts allow you to define deployment scripts, addresses by chain, fixtures settings for testing, and more.**

Expand Down Expand Up @@ -124,7 +124,6 @@ And running this on ``mainnet-fork`` will get the resulting output:
The key here, was the ``mainifest_contract``, which does a lot of things under the hood, including:

- Deploys a contract if one doesn't exist
- Allows us to get fixtures for testing
- Returns the named contract at it's address if it's on a chain we recognize
- Sets up local testing environments for us to test our contracts

Expand Down