Merge branch 'develop' into rpatel/temp-run-logger

Author: rushilpatel0

.github/actions/setup-environment/action.yml

@@ -26,5 +26,5 @@ runs:
     - name: Install codecov
       shell: bash
       run: |
-        uv tool install [email protected] --python 3.10
+        uv tool install [email protected]
         uv tool update-shell

.github/workflows/mypy.yml

@@ -25,7 +25,7 @@ jobs:
 
       - name: Get changed files
         id: changed-files
-        uses: tj-actions/[email protected].7
+        uses: tj-actions/[email protected].8
 
       - name: Filter Python files
         id: filter-python

.github/workflows/release.yml

@@ -72,7 +72,7 @@ jobs:
 
       # TODO: add cbuildwheel cache
       - name: Build wheel
-        uses: pypa/cibuildwheel@v2.22.0
+        uses: pypa/cibuildwheel@v2.23.0
         env:
           CIBW_BUILD: "*cp3${{ matrix.python }}*"
 

.gitignore

@@ -30,6 +30,7 @@ supabase/config.toml
 **/scripts/*.md
 **/scripts/Personal/*
 **/infrastructure/aws_infra/.terraform/*
+pyrightconfig.json
 Edwards Scratchpad.ipynb
 
 # Allowing .env files to exist in repository, but not allowing updates

.pre-commit-config.yaml

@@ -80,27 +80,13 @@ repos:
     rev: 39.169.3
     hooks:
       - id: renovate-config-validator
+
   - repo: https://github.com/astral-sh/uv-pre-commit
     rev: "0.5.31"
     hooks:
       - id: uv-sync
         args: ["--frozen", "--all-packages", "--all-extras"]
 
-  - repo: "local"
-    hooks:
-      # Disabled as part of LFS removal.
-      # - id: disallowed-words-check
-      #   name: Check for disallowed words
-      #   entry: scripts/disallowed-words-check.sh
-      #   language: script
-      #   files: ''  # Check all files
-      - id: generate-runner-imports
-        name: Generate Runner Imports
-        entry: bash -c "uv run --frozen python -m codegen.gscli.cli generate runner-imports src/codegen/shared/compilation/function_imports.py"
-        language: system
-        pass_filenames: false
-        always_run: true
-
   - repo: https://github.com/hukkin/mdformat
     rev: 0.7.22  # Use the ref you want to point at
     hooks:

CONTRIBUTING.md

@@ -39,7 +39,7 @@ uv sync --dev
 > [!TIP]
 >
 > - If sync fails with `missing field 'version'`, you may need to delete lockfile and rerun `rm uv.lock && uv sync --dev`.
-> - If sync fails with failed compilation, you may need to install clang and rerun `uv sync --dev`.
+> - If sync fails with failed compilation, you may need to install dependencies (see [install-deps.sh](scripts/install-deps.sh)) and rerun `uv sync --dev`.
 
 ### Running Tests
 

README.md

@@ -49,7 +49,7 @@ We support
 - macOS and Linux
   - macOS is supported
   - Linux is supported on x86_64 and aarch64 with glibc 2.34+
-  - Windows is not supported
+  - Windows is supported via WSL. See [here](https://docs.codegen.com/building-with-codegen/codegen-with-wsl) for more details.
 - Python, Typescript, Javascript and React codebases
 
 ```

architecture/2. parsing/B. AST Construction.md

@@ -74,4 +74,4 @@ Statements have another layer of complexity. They are essentially pattern based
 
 ## Next Step
 
-After the AST is constructed, the system moves on to [Import Resolution](../3.%20imports-exports/A.%20Imports.md) to analyze module dependencies and resolve symbols across files.
+After the AST is constructed, the system moves on to [Directory Parsing](./C.%20Directory%20Parsing.md) to build a hierarchical representation of the codebase's directory structure.

architecture/2. parsing/C. Directory Parsing.md

@@ -0,0 +1,50 @@
+# Directory Parsing
+
+The Directory Parsing system is responsible for creating and maintaining a hierarchical representation of the codebase's directory structure in memory. Directories do not hold references to the file itself, but instead holds the names to the files and does a dynamic lookup when needed.
+
+In addition to providing a more cohesive API for listing directory files, the Directory API is also used for [TSConfig](../3.%20imports-exports/C.%20TSConfig.md)-based (Import Resolution)[../3.%20imports-exports/A.%20Imports.md].
+
+## Core Components
+
+The Directory Tree is constructed during the initial build_graph step in codebase_context.py, and is recreated from scratch on every re-sync. More details are below:
+
+## Directory Tree Construction
+
+The directory tree is built through the following process:
+
+1. The `build_directory_tree` method in `CodebaseContext` is called during graph initialization or when the codebase structure changes.
+1. The method iterates through all files in the repository, creating directory objects for each directory path encountered.
+1. For each file, it adds the file to its parent directory using the `_add_file` method.
+1. Directories are created recursively as needed using the `get_directory` method with create_on_missing=True\`.
+
+## Directory Representation
+
+The `Directory` class provides a rich interface for working with directories:
+
+- **Hierarchy Navigation**: Access parent directories and subdirectories
+- **File Access**: Retrieve files by name or extension
+- **Symbol Access**: Find symbols (classes, functions, etc.) within files in the directory
+- **Directory Operations**: Rename, remove, or update directories
+
+Each `Directory` instance maintains:
+
+- A reference to its parent directory
+- Lists of files and subdirectories
+- Methods to recursively traverse the directory tree
+
+## File Representation
+
+Files are represented by the `File` class and its subclasses:
+
+- `File`: Base class for all files, supporting basic operations like reading and writing content
+- `SourceFile`: Specialized class for source code files that can be parsed into an AST
+
+Files maintain references to:
+
+- Their parent directory
+- Their content (loaded dynamically to preserve the source of truth)
+- For source files, the parsed AST and symbols
+
+## Next Step
+
+After the directory structure is parsed, the system can perform [Import Resolution](../3.%20imports-exports/A.%20Imports.md) to analyze module dependencies and resolve symbols across files.

architecture/3. imports-exports/A. Imports.md

@@ -1,7 +1,60 @@
 # Import Resolution
 
-TODO
+Import resolution follows AST construction in the code analysis pipeline. It identifies dependencies between modules and builds a graph of relationships across the codebase.
+
+> NOTE: This is an actively evolving part of Codegen SDK, so some details here may be imcomplete, outdated, or incorrect.
+
+## Purpose
+
+The import resolution system serves these purposes:
+
+1. **Dependency Tracking**: Maps relationships between files by resolving import statements.
+1. **Symbol Resolution**: Connects imported symbols to their definitions.
+1. **Module Graph Construction**: Builds a directed graph of module dependencies.
+1. **(WIP) Cross-Language Support**: Provides implementations for different programming languages.
+
+## Core Components
+
+### ImportResolution Class
+
+The `ImportResolution` class represents the outcome of resolving an import statement. It contains:
+
+- The source file containing the imported symbol
+- The specific symbol being imported (if applicable)
+- Whether the import references an entire file/module
+
+### Import Base Class
+
+The `Import` class is the foundation for language-specific import implementations. It:
+
+- Stores metadata about the import (module path, symbol name, alias)
+- Provides the abstract `resolve_import()` method
+- Adds symbol resolution edges to the codebase graph
+
+### Language-Specific Implementations
+
+#### Python Import Resolution
+
+The `PyImport` class extends the base `Import` class with Python-specific logic:
+
+- Handles relative imports
+- Supports module imports, named imports, and wildcard imports
+- Resolves imports using configurable resolution paths and `sys.path`
+- Handles special cases like `__init__.py` files
+
+#### TypeScript Import Resolution
+
+The `TSImport` class implements TypeScript-specific resolution:
+
+- Supports named imports, default imports, and namespace imports
+- Handles type imports and dynamic imports
+- Resolves imports using TSConfig path mappings
+- Supports file extension resolution
+
+## Implementation
+
+After file and directory parse, we loop through all import nodes and perform `add_symbol_resolution_edge`. This then invokes the language-specific `resolve_import` method that converts the import statement into a resolvable `ImportResolution` object (or None if the import cannot be resolved). This import symbol and the `ImportResolution` object are then used to add a symbol resolution edge to the graph, where it can then be used in future steps to resolve symbols.
 
 ## Next Step
 
-After import resolution, the system analyzes [Export Analysis](./B.%20Exports.md) and handles [TSConfig Support](./C.%20TSConfig.md) for TypeScript projects. This is followed by comprehensive [Type Analysis](../4.%20type-analysis/A.%20Type%20Analysis.md).
+After import resolution, the system analyzes [Export Analysis](./B.%20Exports.md) and handles [TSConfig Support](./C.%20TSConfig.md) for TypeScript projects. This is followed by [Type Analysis](../4.%20type-analysis/A.%20Type%20Analysis.md).