-
Notifications
You must be signed in to change notification settings - Fork 326
Rust Client Implementation #2558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: canary
Are you sure you want to change the base?
Conversation
- 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
|
🌿 Preview your docs: https://boundary-preview-41c098c0-e63b-4e83-9891-c2a54e99a30e.docs.buildwithfern.com |
|
🌿 Preview your docs: https://boundary-preview-dba2e81f-6ad5-4f53-88bd-56ff2f42b7a7.docs.buildwithfern.com |
…te rust integration tests readme
|
🌿 Preview your docs: https://boundary-preview-10079df6-c437-4164-b138-230b7131db9a.docs.buildwithfern.com |
|
🌿 Preview your docs: https://boundary-preview-52e44a9c-1a99-4deb-8ac6-bc2f73ad4bf4.docs.buildwithfern.com |
PR Summary
This pull request introduces integration tests for the Rust client generator in the
bamlrepository. 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
Next Steps