Skip to content

Commit

Permalink
docs: apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Neil Campbell <neil.campbell@makerx.com.au>
  • Loading branch information
aorumbayev and neilcampbell authored Feb 19, 2025
1 parent 8b3af0f commit 6d25c3d
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion docs/html/_sources/capabilities/app-deploy.md.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
6 changes: 3 additions & 3 deletions docs/source/capabilities/app-deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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 ...
```

Expand Down
2 changes: 1 addition & 1 deletion docs/source/v3-migration-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit 6d25c3d

Please sign in to comment.