Avoid direct dependency on shaded EntityTaskResult - #1679
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (11)
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (2)
📝 WalkthroughWalkthroughThe Folia completion path now classifies task results by checking whether the status is an enum named ChangesFolia task result handling
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Refactor Merge Risk: ⚪ Minimal · up to Folia task completion preserves the existing success and fallback behavior, and the reviewed changes show no concrete merge-blocking regression. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to Normal success and retirement handling appears preserved, but the new success rule accepts any enum named SUCCESS. The scheduler supplies production results, and its exact result contract has not been verified. Retained concerns
Security review detailsSecurity Blast Radius
Trust Boundaries and Controls
Resilience and Maintainability Implications
Hardening Proposals
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 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 |
Summary
EntityTaskResultdirectly in VotingPlugin production codeSUCCESSenum nameWhy
SimpleAPI relocates FoliaLib during shading. Eclipse/m2e can resolve SimpleAPI differently from Maven (especially with workspace projects / SNAPSHOT artifacts), which makes
com.bencodez.simpleapi.folialib.enums.EntityTaskResultfail to resolve even though Maven packaging sees the shaded class.This keeps the runtime behavior unchanged while removing the fragile compile-time dependency on that relocated enum class.
Validation
com.bencodez.simpleapi.folialib.enums.EntityTaskResultSummary by CodeRabbit