feat(mister): add .chd extension to 3DO launcher#786
Conversation
📝 WalkthroughWalkthroughThe 3DO launcher in the MiSTer platform is updated to recognize Changes3DO Launcher File Extension Support
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 `@pkg/platforms/mister/launchers.go`:
- Around line 607-611: New .chd support for systemdefs.System3DO (the Launch
entry using launch(pl, systemdefs.System3DO)) lacks a regression test; add a
test that verifies files with a .chd extension are matched to
systemdefs.System3DO by the launcher matcher. Create a unit test following
pkg/testing/README.md patterns that constructs a launcher registry or calls the
matcher used by pkg/platforms/mister/launchers.go (the Launch/matching logic for
System3DO), supplies sample filenames including "game.chd" and asserts the
matcher returns systemdefs.System3DO (and that other extensions like .iso/.cue
still match), and place it alongside related tests to satisfy the TESTING.md
guidelines.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 224bf43a-8766-40cc-aaf7-2002b95ac1dc
📒 Files selected for processing (1)
pkg/platforms/mister/launchers.go
| ID: systemdefs.System3DO, | ||
| SystemID: systemdefs.System3DO, | ||
| Folders: []string{"3DO"}, | ||
| Extensions: []string{".iso", ".cue"}, | ||
| Extensions: []string{".iso", ".cue", ".chd"}, | ||
| Launch: launch(pl, systemdefs.System3DO), |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major | ⚡ Quick win
Add a regression test for 3DO .chd matching.
Line 610 introduces new launcher matching behavior, but there’s no accompanying test proving .chd files are recognized for systemdefs.System3DO.
As per coding guidelines, "**/*.go: Write tests for all new code — follow TESTING.md and pkg/testing/README.md patterns".
🤖 Prompt for 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.
In `@pkg/platforms/mister/launchers.go` around lines 607 - 611, New .chd support
for systemdefs.System3DO (the Launch entry using launch(pl,
systemdefs.System3DO)) lacks a regression test; add a test that verifies files
with a .chd extension are matched to systemdefs.System3DO by the launcher
matcher. Create a unit test following pkg/testing/README.md patterns that
constructs a launcher registry or calls the matcher used by
pkg/platforms/mister/launchers.go (the Launch/matching logic for System3DO),
supplies sample filenames including "game.chd" and asserts the matcher returns
systemdefs.System3DO (and that other extensions like .iso/.cue still match), and
place it alongside related tests to satisfy the TESTING.md guidelines.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
.chdto the MiSTer 3DO launcher's recognised extensions alongside.isoand.cue.Summary by CodeRabbit