fix(parser): bind Aura token creators to attached player - #7326
Conversation
|
Warning Review limit reached
Next review available in: 21 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughOracle effect parsing recognizes enchanted opponents as attached subjects and propagates that subject through contiguous shared token effects. Regression tests cover chained Clue, Food, and Junk token creation. ChangesOracle subject binding
Estimated code review effort: 3 (Moderate) | ~20 minutes Mergeability Score: ⚪ Minimal · up to No actionable merge-blocking risk is identified for the current change; it is merge-ready after normal checks. Possibly related PRs
Suggested labels: Sequence Diagram(s)sequenceDiagram
participant OracleParser
participant SubjectApplication
participant TokenEffects
OracleParser->>SubjectApplication: parse enchanted opponent subject
SubjectApplication->>TokenEffects: apply TargetFilter::AttachedTo
TokenEffects->>TokenEffects: propagate subject through Clue, Food, and Junk
TokenEffects-->>OracleParser: end chain after Junk
🚥 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 |
1989fbd to
63a15b1
Compare
|
Generated for head Parse changes introduced by this PR · 1 card(s), 2 signature(s) (baseline: main
|
73aedcf to
1ac3dbf
Compare
One conflict, in the import list of oracle_effect/subject.rs: this branch added EffectScope for the broadcast ForceAttack arm while phase-rs#7326 / phase-rs#7322 / phase-rs#7333 added ObjectScope. Both are needed; kept both.
Summary by CodeRabbit