fix: Unity CLI Loop assemblies no longer expose legacy uLoopMCP names#1230
Conversation
Rename remaining tracked asmdef asset filenames to UnityCLILoop while preserving their .meta contents and GUIDs. Update filename-based tests so future cleanup catches legacy asset names.
Update remaining asmdef names to UnityCLILoop and align friend assembly and scene references with the new assembly identities. Preserve migration support for old name-based runtime references so third-party asmdefs can still be repaired.
Run the sample tool assertions through an isolated execution service so the tests no longer contend with the shared run-tests execution slot.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (16)
📒 Files selected for processing (36)
📝 WalkthroughWalkthroughThis PR renames the legacy ChangesNamespace Migration from uLoopMCP to UnityCLILoop
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Summary
User Impact
Changes
Verification