fix(cli): keep default generated SDK inside project - #4522
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
Included review availability: Your plan provides up to 8 included reviews per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe generator default output directory changes from the project parent to the project root. Rust tests verify that ChangesGenerator output path
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: 🔵 Low · up to When Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
⏭️ Performance benchmarks were skippedPerf benchmarks (CodSpeed) are opt-in on pull requests — they no longer run on every push. They always run automatically after merge to To run them on this PR, do any of the following, then push a commit (or re-run CI):
|
Binary size checks passed✅ 7 passed
Generated by |
|
@coderabbitai review |
|
|
@coderabbitai review |
|
|
@coderabbitai review |
|
|
@coderabbitai rate limit |
|
Your plan includes PR reviews subject to rate limits. More reviews will be available in 38 minutes. |
|
@coderabbitai review |
Rate Limit Exceeded
|
|
@coderabbitai review |
|
|
@coderabbitai rate limit |
|
Your plan includes PR reviews subject to rate limits. More reviews will be available in 50 seconds. |
|
@coderabbitai review |
|
|
@coderabbitai full review |
|
|
@coderabbitai full review |
✅ Action performedFull review finished. |
Summary
output_dirto the BAML project root so the generatedbaml_sdkstays inside the projectoutput_dirbehaviorRoot cause
Generator configuration moved from source files, where paths were relative to
baml_src, tobaml.toml, where paths resolve relative to the project root. The former..default was retained during that migration, changing its effective destination to the parent of the project.Validation
cargo test -p baml_cli generator_output_defaults_to_project_rootcargo test -p baml_cli render_keyword_generatorcargo test -p baml_cli --test exit_code_e2e generate_rust_default_output_stays_inside_projectcargo test -p baml_bridge --libcargo clippy -p baml_cli --all-targets -- -D warningscargo fmt --check -- --config imports_granularity=Crate --config group_imports=StdExternalCrateFixes #4376
Summary by CodeRabbit
Bug Fixes
baml_sdkfolder by default.Documentation
output_dirdefaults to the current project directory.