chore(proto): stop generating Rust for in-design proto packages - #548
Open
yordis wants to merge 1 commit into
Open
chore(proto): stop generating Rust for in-design proto packages#548yordis wants to merge 1 commit into
yordis wants to merge 1 commit into
Conversation
The session and usage schemas are still being shaped, so binding them into the Rust workspace made a hand-written validation and codec layer track fields that keep moving, with no crate consuming it. Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
PR SummaryMedium Risk Overview The Net effect: session and usage proto can churn without regenerating Rust or breaking workspace consumers that never enabled session codegen; stable packages (schedules, agents, decider) keep generating as before. Reviewed by Cursor Bugbot for commit 20db8d0. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (325)
📒 Files selected for processing (10)
💤 Files with no reviewable changes (7)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe change stops generating session and usage protobuf code. It removes the ChangesSession proto removal
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This change stops generating unused Rust code for in-design schema packages while retaining schema validation and compatibility checks; no actionable merge-blocking risk remains after normal checks and review. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (1 skipped: 1 unsupported.) ✨ 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 |
|
Code Coverage SummaryDetailsDiff against mainResults for commit: 20db8d0 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The session and usage schemas are still in active design, but generating Rust for them tied the workspace to shapes that keep moving: a hand-written validation and codec layer had to be re-derived on every field rename, while no crate in the workspace enabled the features that consumed it. Excluding those packages from codegen lets the schema churn freely while
buf lint,format,build, andbreakingkeep covering them in full. ADR#0035 stays the source of truth for the session append-boundary rules, so the removed layer is recoverable once a consumer crate exists to justify it.Related