This directory contains Architecture Decision Records (ADRs) for the python2ts project.
An Architecture Decision Record captures an important architectural decision made along with its context and consequences.
| ID | Title | Status | Date |
|---|---|---|---|
| ADR-0001 | Use @lezer/python as Parser | Accepted | 2026-01-16 |
| ADR-0002 | Runtime Namespace Design (py.*) | Superseded | 2026-01-16 |
| ADR-0003 | Preserve Python Operator Semantics | Accepted | 2026-01-16 |
| ADR-0004 | Testing Strategy with Vitest | Accepted | 2026-01-16 |
| ADR-0005 | ESM-Only Distribution | Accepted | 2026-01-16 |
| ADR-0006 | Python Type Hints to TypeScript | Accepted | 2026-01-16 |
| ADR-0007 | @dataclass Transformation Strategy | Accepted | 2026-01-16 |
| ADR-0008 | itertools: Eager Arrays vs. Lazy | Accepted | 2026-01-17 |
| ADR-0009 | Subpath Exports Architecture | Accepted | 2026-01-18 |
| ADR-0010 | Monorepo Package Structure | Accepted | 2026-01-18 |
| ADR-0011 | camelCase API Convention | Accepted | 2026-01-18 |
| ADR-0012 | Async Filesystem API | Accepted | 2026-01-21 |
When adding a new ADR, use the following template:
# ADR-XXXX: Title
## Status
Proposed | Accepted | Deprecated | Superseded by [ADR-XXXX](./xxxx-title.md)
## Context
What is the issue that we're seeing that is motivating this decision or change?
## Decision
What is the change that we're proposing and/or doing?
## Consequences
What becomes easier or more difficult to do because of this change?