feat(mister): add DualRAM alt launchers for 3DO, Jaguar, PSX, Saturn#711
feat(mister): add DualRAM alt launchers for 3DO, Jaguar, PSX, Saturn#711wizzomafizzo merged 1 commit intomainfrom
Conversation
Adds four alt launchers targeting cores from the TheJesusFish/Dual-Ram-Console-Cores repo, which distributes dual-SDRAM builds into /media/fat/_Console (Dual SDRAM)/. Users can manually assign these as alt launchers for tokens once the folder is present on their MiSTer.
📝 WalkthroughWalkthroughFour new MiSTer launcher definitions are added for DualRAM variants of 3DO, Jaguar, PSX, and Saturn systems. Each launcher registers an alternate core with its corresponding Dual SDRAM RBF path. A test validates the presence and correct SystemID associations of these new launchers. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
pkg/platforms/mister/launchers_test.go (1)
489-497: Prefersystemdefsconstants instead of rawSystemIDstrings in the case table.Using constants here improves refactor safety and keeps the test aligned with the launcher definitions.
♻️ Suggested update
cases := []struct { id string systemID string }{ - {"DualRAM3DO", "3DO"}, - {"DualRAMJaguar", "Jaguar"}, - {"DualRAMPSX", "PSX"}, - {"DualRAMSaturn", "Saturn"}, + {"DualRAM3DO", systemdefs.System3DO}, + {"DualRAMJaguar", systemdefs.SystemJaguar}, + {"DualRAMPSX", systemdefs.SystemPSX}, + {"DualRAMSaturn", systemdefs.SystemSaturn}, }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@pkg/platforms/mister/launchers_test.go` around lines 489 - 497, Update the test table `cases` in launchers_test.go to use the `systemdefs` package constants for the systemID field instead of raw string literals; replace the "3DO", "Jaguar", "PSX", "Saturn" values with the corresponding `systemdefs` constants (e.g., the constant names that represent those SystemID values) so the `cases` slice uses `systemdefs.<Constant>` for each `systemID`, ensuring the test stays refactor-safe and aligned with launcher definitions.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@pkg/platforms/mister/launchers_test.go`:
- Around line 489-497: Update the test table `cases` in launchers_test.go to use
the `systemdefs` package constants for the systemID field instead of raw string
literals; replace the "3DO", "Jaguar", "PSX", "Saturn" values with the
corresponding `systemdefs` constants (e.g., the constant names that represent
those SystemID values) so the `cases` slice uses `systemdefs.<Constant>` for
each `systemID`, ensuring the test stays refactor-safe and aligned with launcher
definitions.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 137801a0-4581-4806-98c4-49c3599d1f80
📒 Files selected for processing (2)
pkg/platforms/mister/launchers.gopkg/platforms/mister/launchers_test.go
DualRAM3DO,DualRAMJaguar,DualRAMPSX, andDualRAMSaturnalt launchers targeting cores from the TheJesusFish/Dual-Ram-Console-Cores repo, which distributes dual-SDRAM builds into/media/fat/_Console (Dual SDRAM)/.launchAltCorewith the path_Console (Dual SDRAM)/<Core>— the existing RBF cache picks up the folder automatically (any_-prefixed dir under/media/fatis scanned) and falls back to the canonical system core if the dual-ram RBF is absent.Folders/Extensionsset; slot config is inherited from the canonical system launcher viacores.GetCore(systemID), matching the pattern used by LLAPI and PWM alt launchers.mister.CreateLaunchers.Summary by CodeRabbit
Release Notes
New Features
Tests