From 26a6717e763811e0f9c23818d842ab0ea2fb2a99 Mon Sep 17 00:00:00 2001 From: Rob Moore Date: Tue, 24 Jan 2023 01:51:39 +0800 Subject: [PATCH] docs: Added missing recommendation for type-safe client --- .../2023-01-12_smart-contract-deployment.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/architecture-decisions/2023-01-12_smart-contract-deployment.md b/docs/architecture-decisions/2023-01-12_smart-contract-deployment.md index 96f9bf5b..b29588dc 100644 --- a/docs/architecture-decisions/2023-01-12_smart-contract-deployment.md +++ b/docs/architecture-decisions/2023-01-12_smart-contract-deployment.md @@ -155,6 +155,8 @@ console.log(result); // Hello, World! To be fair, you could have a middle-ground and load the ABI json to populate the `method` parameter of the `addMethodCall` call, but the `methodArgs` are still problematic and there is still no intellisense. +The suggested implementation for AlgoKit v1 is to provide a basic type-safe TypeScript client (leveraging either the MakerX TypeScript generator or [beaker-ts](https://github.com/algorand-devrel/beaker-ts)) and leave Python with the semi-typed implementation that Beaker currently exposes (with implementing a fully typed Python client as a future implementation effort). + ### Deployment and development decoupling As discussed above, decoupling deployment and development of smart contracts is a useful technique.