feat(eloot.lic): v2.9.0 add keep transmogs feature#2311
Conversation
Updated Lich requirement and version, added feature to keep transmogs, and modified related logic in the script.
📝 WalkthroughWalkthroughThe PR adds a transmog detection feature to the ELoot script. A new ChangesTransmog Detection & Keeping
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/eloot.lic`:
- Around line 3359-3360: The is_transmog? method currently does item.type =~
/jewelry|clothing/ which will raise if item.type is nil; update is_transmog? to
coerce the type to a safe string (e.g., use item.type.to_s or a
nil-to-empty-string guard) before applying the =~ match and keep the existing
checks for after_name to prevent nil errors during sell/dump flows when
keep_transmogs is enabled.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
Updated Lich requirement and version, added feature to keep transmogs, and modified related logic in the script.
Summary by CodeRabbit
New Features
Improvements