Skip to content

Create TypeScript Examples #26

@yaythomas

Description

@yaythomas

Overview

The examples/typescript/ directory currently contains placeholder files with "Coming soon..." comments. These need to be replaced with actual working TypeScript examples that mirror the functionality demonstrated in the Python examples.

Current State

All TypeScript example files (.ts) in the following directories contain only placeholder content:

  • examples/typescript/advanced/error-handling/ (32 files)
  • examples/typescript/advanced/serialization/ (29 files)
  • examples/typescript/advanced/testing-modes/ (8 files)
  • examples/typescript/best-practices/ (48 files)
  • examples/typescript/core/callbacks/ (23 files)
  • examples/typescript/core/child-contexts/ (14 files)
  • examples/typescript/core/invoke/ (20 files)
  • examples/typescript/core/logger/ (25 files)
  • examples/typescript/core/map/ (15 files)
  • examples/typescript/core/parallel/ (28 files)
  • examples/typescript/core/steps/ (18 files)
  • examples/typescript/core/wait/ (18 files)
  • examples/typescript/getting-started/ (5 files)
  • examples/typescript/index/ (1 file)
  • examples/typescript/testing-patterns/basic-tests/ (27 files)
  • examples/typescript/testing-patterns/complex-workflows/ (26 files)
  • examples/typescript/testing-patterns/stores/ (3 files)

Total: ~360 placeholder files

Requirements

Each TypeScript example should:

  1. Implement the same functionality as its Python counterpart in examples/python/
  2. Follow TypeScript best practices and idioms
  3. Use appropriate TypeScript types and interfaces
  4. Include relevant comments explaining key concepts
  5. Be syntactically correct and runnable (where applicable)
  6. Demonstrate the AWS Lambda Durable Functions SDK for TypeScript

Acceptance Criteria

  • All .ts files in examples/typescript/ contain working code examples
  • Examples accurately translate Python functionality to TypeScript
  • Code follows TypeScript conventions and style guidelines
  • Examples are consistent with the documentation in docs/
  • No "Coming soon..." placeholders remain

Notes

  • The Python examples in examples/python/ should serve as the reference of expected outputs
  • Consider TypeScript-specific patterns where direct translation isn't idiomatic
  • Maintain the same file structure and naming conventions

Sub-tasks

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions