diff --git a/docs/html/_sources/capabilities/app-deploy.md.txt b/docs/html/_sources/capabilities/app-deploy.md.txt index 1310ddd..8808088 100644 --- a/docs/html/_sources/capabilities/app-deploy.md.txt +++ b/docs/html/_sources/capabilities/app-deploy.md.txt @@ -68,7 +68,7 @@ An example of the ARC-2 transaction note that is attached as an app creation / u ALGOKIT_DEPLOYER:j{name:"MyApp",version:"1.0",updatable:true,deletable:false} ``` -> NOTE: Starting from v3.0.0, AlgoKit Utils no longer automatically increments the contract version by default. It is end user's responsibility to explicitly manage versioning of their smart contracts (if desired). +> NOTE: Starting from v3.0.0, AlgoKit Utils no longer automatically increments the contract version by default. It is the user's responsibility to explicitly manage versioning of their smart contracts (if desired). ## Lookup deployed apps by name @@ -201,11 +201,11 @@ Below is a sample in [Algorand Python SDK](https://github.com/algorandfoundation # ... your contract code ... @arc4.baremethod(allow_actions=["UpdateApplication"]) def update(self) -> None: - assert TemplateVar[bool](UPDATABLE_TEMPLATE_NAME) + assert TemplateVar[bool]("UPDATABLE") @arc4.baremethod(allow_actions=["DeleteApplication"]) def delete(self) -> None: - assert TemplateVar[bool](DELETABLE_TEMPLATE_NAME) + assert TemplateVar[bool]("DELETABLE") # ... your contract code ... ``` diff --git a/docs/html/_sources/v3-migration-guide.md.txt b/docs/html/_sources/v3-migration-guide.md.txt index 3953381..5797646 100644 --- a/docs/html/_sources/v3-migration-guide.md.txt +++ b/docs/html/_sources/v3-migration-guide.md.txt @@ -249,7 +249,7 @@ result = algorand.send.asset_opt_in( 4. **Application Client** - Split into `AppClient`, `AppDeployer` and `AppFactory` - - `deploy` method in `AppFactory`/`AppDeployer` no longer auto increments the contract version by default. It is end user's responsibility to explicitly manage versioning of their smart contracts (if desired). + - `deploy` method in `AppFactory`/`AppDeployer` no longer auto increments the contract version by default. It is the user's responsibility to explicitly manage versioning of their smart contracts (if desired). - New intuitive structured interface for creating or sending `AppCall`|`AppMethodCall` transactions - ARC-56 support along with automatic conversion of specs from ARC-32 to ARC-56 diff --git a/docs/html/capabilities/app-deploy.html b/docs/html/capabilities/app-deploy.html index 6d0713d..e08928b 100644 --- a/docs/html/capabilities/app-deploy.html +++ b/docs/html/capabilities/app-deploy.html @@ -386,7 +386,7 @@
# ... your contract code ...
@arc4.baremethod(allow_actions=["UpdateApplication"])
def update(self) -> None:
- assert TemplateVar[bool](UPDATABLE_TEMPLATE_NAME)
+ assert TemplateVar[bool]("UPDATABLE")
@arc4.baremethod(allow_actions=["DeleteApplication"])
def delete(self) -> None:
- assert TemplateVar[bool](DELETABLE_TEMPLATE_NAME)
+ assert TemplateVar[bool]("DELETABLE")
# ... your contract code ...
Split into AppClient
, AppDeployer
and AppFactory
deploy
method in AppFactory
/AppDeployer
no longer auto increments the contract version by default. It is end user’s responsibility to explicitly manage versioning of their smart contracts (if desired).
deploy
method in AppFactory
/AppDeployer
no longer auto increments the contract version by default. It is the user’s responsibility to explicitly manage versioning of their smart contracts (if desired).
New intuitive structured interface for creating or sending AppCall
|AppMethodCall
transactions
ARC-56 support along with automatic conversion of specs from ARC-32 to ARC-56