Skip to content

Conversation

@h4n0
Copy link
Collaborator

@h4n0 h4n0 commented Oct 2, 2025

PR Summary

This pull request introduces integration tests for the Rust client generator in the baml repository. The primary goal is to ensure that the Rust client generator produces correct and reliable client code by testing its functionality against a suite of integration scenarios.

Key Changes

  • Adds integration tests specifically targeting the Rust client generator.
  • Verifies correctness of generated client code in various usage scenarios.
  • Establishes a foundation for future enhancements and automated verification of Rust client generation.

Next Steps

  • Add media types support

CeciliaZ030 and others added 30 commits August 19, 2025 22:09
- Add BAML-RUST.md: Comprehensive analysis of Rust client implementation approach
- Add BAML-GO.md: Deep dive into Go client FFI architecture and performance
- Document why OpenAPI-generated Rust clients are limited (~60% feature loss)
- Outline implementation plan for native Rust client generator
- Compare direct FFI clients vs HTTP-based clients

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
- Refactor Rust client generation templates for improved code structure
- Remove redundant runtime.rs.j2 template
- Update generator configuration to support Rust client output
- Add Rust generator to BAML test configuration

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
➜  generators: ✗ cargo test --package generators-rust
…ample (failing) semantic_streaming and unions
@h4n0 h4n0 temporarily deployed to boundary-tools-dev October 13, 2025 13:01 — with GitHub Actions Inactive
@h4n0 h4n0 temporarily deployed to boundary-tools-dev October 13, 2025 13:01 — with GitHub Actions Inactive
@h4n0 h4n0 temporarily deployed to boundary-tools-dev October 13, 2025 13:01 — with GitHub Actions Inactive
@github-actions
Copy link

@github-actions
Copy link

@h4n0 h4n0 temporarily deployed to boundary-tools-dev October 14, 2025 14:33 — with GitHub Actions Inactive
@h4n0 h4n0 had a problem deploying to boundary-tools-dev October 14, 2025 14:33 — with GitHub Actions Error
@h4n0 h4n0 temporarily deployed to boundary-tools-dev October 14, 2025 14:33 — with GitHub Actions Inactive
@github-actions
Copy link

@h4n0 h4n0 temporarily deployed to boundary-tools-dev October 14, 2025 14:46 — with GitHub Actions Inactive
@h4n0 h4n0 temporarily deployed to boundary-tools-dev October 14, 2025 14:46 — with GitHub Actions Inactive
@h4n0 h4n0 temporarily deployed to boundary-tools-dev October 14, 2025 14:46 — with GitHub Actions Inactive
@github-actions
Copy link

@github-actions
Copy link

@h4n0 h4n0 temporarily deployed to boundary-tools-dev October 15, 2025 14:43 — with GitHub Actions Inactive
@h4n0 h4n0 temporarily deployed to boundary-tools-dev October 15, 2025 14:43 — with GitHub Actions Inactive
@h4n0 h4n0 temporarily deployed to boundary-tools-dev October 15, 2025 14:43 — with GitHub Actions Inactive
@github-actions
Copy link

@github-actions
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants