feat: ts api jinja generator

[aorumbayev]

Initial version of ts api jinja generator and resulting algod/indexer clients based off algo-fetch from awesomealgo.

[aorumbayev]

@neilcampbell note current version duplicates SignedTransaction object from core from future branch on utils - for the time being until its movied to the monorepo

[Copilot]

Pull Request Overview

This PR introduces TypeScript API client generation for Algorand algod and indexer services through a Jinja-based code generator. The implementation creates comprehensive TypeScript clients that support modern features like msgpack encoding, BigInt handling, and request/response transformation.

Key changes:

• Add TypeScript code generation commands for algod and indexer clients
• Implement comprehensive client libraries with typed models and APIs
• Add msgpack support for Algorand-compliant transaction encoding/decoding
• Include manual test suites for client functionality validation

Reviewed Changes

Copilot reviewed 232 out of 238 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
tools/api_tools/src/main.rs	Adds new CLI commands for TypeScript client generation with cleaning, formatting, and building steps
packages/typescript//src/models/.ts	Generated TypeScript type definitions for all API models with proper BigInt support
packages/typescript//src/core/.ts	Core HTTP client infrastructure with msgpack, JSON parsing, and request handling
packages/typescript//src/apis/.ts	Generated API service classes with comprehensive endpoint coverage
packages/typescript//tests/.ts	Manual test suites for client functionality verification

Comments suppressed due to low confidence (1)

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[PatrickDinh]

@aorumbayev I noticed that the approvalProgram and clearStateProgram when calling getApplicationById are string while the rust version is Vec<u8>. The reason is that the rust version uses serde to automatically convert the base64 string returned by algod to Vec. Do you remember the reason why it was done that way in Rust?

[PatrickDinh]

hi @aorumbayev, I tested the output from this branch and found some possible improvements

• The type field should be number

export type TealValue = {
  /**
   * \[tt\] value type. Value `1` refers to **bytes**, value `2` refers to **uint**
   */
  type: bigint;

  /**
   * \[tb\] bytes value.
   */
  bytes: string;

  /**
   * \[ui\] uint value.
   */
  uint: bigint;
};

• In AssetParams, fields unitNameB64, nameB64 and urlB64 should be Uint8Array

[aorumbayev]

hi @aorumbayev, I tested the output from this branch and found some possible improvements

• The type field should be number

export type TealValue = {
  /**
   * \[tt\] value type. Value `1` refers to **bytes**, value `2` refers to **uint**
   */
  type: bigint;

  /**
   * \[tb\] bytes value.
   */
  bytes: string;

  /**
   * \[ui\] uint value.
   */
  uint: bigint;
};

• In AssetParams, fields unitNameB64, nameB64 and urlB64 should be Uint8Array

should be fixed now

[aorumbayev]

@aorumbayev I noticed that the approvalProgram and clearStateProgram when calling getApplicationById are string while the rust version is Vec<u8>. The reason is that the rust version uses serde to automatically convert the base64 string returned by algod to Vec. Do you remember the reason why it was done that way in Rust?

this should now be consistent with rust, in ts those fields should be uint8arrays and decoder must convert the base64 strings to bytes.

[engineering-ci]

🎉 This PR is included in version 1.0.0-alpha.68 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀