Skip to content

fix wrong name for config option deployer_script #272

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix wrong name for config option deployer_script #272

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
8 changes: 4 additions & 4 deletions docs/source/core_concepts/named_contracts.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ There are a number of flags we can set for our ``NamedContract``:
address = "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"
abi = "ERC20.vy"
abi_from_explorer = true
deployment_script = "script/deploy_erc20.py"
deployer_script = "script/deploy_erc20.py"
force_deploy = false

.. code-tab:: bash ugly-toml
Expand All @@ -80,7 +80,7 @@ There are a number of flags we can set for our ``NamedContract``:
address = "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"
abi = "ERC20.vy"
abi_from_explorer = true
deployment_script = "script/deploy_erc20.py"
deployer_script = "script/deploy_erc20.py"
force_deploy = false
}

Expand All @@ -93,7 +93,7 @@ Let's break these down:
- *Coming soon* ``.vyi`` file path to a Vyper interface
- A "raw" ABI string
- ``abi_from_explorer``: If you want to get the ABI from an explorer. This is useful if you don't have the ABI and you want to get it from a public source. You'll need to set a ``explorer_api_key`` in your ``moccasin.toml``, or an ``EXPLORER_API_KEY`` environment variable.
- ``deployment_script``: The path to the :doc:`deployment script </core_concepts/scripting/deploy>` for this named contract, this will be a shorthand for deploying in the future.
- ``deployer_script``: The path to the :doc:`deployment script </core_concepts/scripting/deploy>` for this named contract, this will be a shorthand for deploying in the future.
- ``force_deploy``: If you want to force deploy the contract when :ref:`manifesting <manifesting>` the contract.

As we know, to interact with a contract, one of the most important things is the ABI. For us to interact with any named contract, we give it an ABI, and we can start interacting with that named contract using the ``manifest_named`` function.
Expand Down Expand Up @@ -134,4 +134,4 @@ And more! Let's read more about the power of ``NamedContract``\s and how they ca
:maxdepth: 2

Manifest Named Contract <named_contracts/manifest_named.rst>