Skip to content

Check mappings UseM3u is enabled #87

Merged
gantoine merged 1 commit intorommapp:mainfrom
matthew-pye:m3u
Feb 1, 2026
Merged

Check mappings UseM3u is enabled #87
gantoine merged 1 commit intorommapp:mainfrom
matthew-pye:m3u

Conversation

@matthew-pye
Copy link
Copy Markdown
Contributor

@matthew-pye matthew-pye commented Jan 31, 2026

-Check UseM3u is enabled in the mapping before using it
-Remove m3u entry when importing games and m3u is not enabled

-Search the string array instead of the directory for m3u
31-01 07:49:35.890|INFO |RomM#RomMInstallController:Directory search took 1630 ticks
31-01 07:49:35.890|INFO |RomM#RomMInstallController:actualRomFiles search took 324 ticks

-Search the string array instead of the directory
-Remove m3u when importing games and m3u is not selected
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @matthew-pye, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the game installation process by improving how M3U playlist files are handled. It ensures that M3U files are only considered and imported when explicitly enabled in the game mapping settings, and streamlines the detection of these files within the existing ROM file list. This leads to more accurate and user-setting-compliant game imports.

Highlights

  • M3U File Handling Logic: The logic for detecting and utilizing M3U files during game installation has been refined to explicitly check if the 'UseM3u' setting is enabled in the mapping.
  • M3U File Search Optimization: The method for finding M3U files has been optimized to search within the already identified 'actualRomFiles' array, rather than performing a separate directory enumeration.
  • Conditional M3U Inclusion: M3U files are now only added to the list of game ROMs if the 'UseM3u' setting is active; otherwise, they are filtered out to prevent incorrect imports.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly refactors the M3U file handling logic during game installation. The changes improve efficiency by searching for M3U files within the already-retrieved list of ROM files instead of re-scanning the directory. The logic to handle cases where M3U is disabled is also more robust now. I have one suggestion to simplify a conditional check and align code formatting for better consistency.

matthew-pye referenced this pull request Feb 1, 2026
Copy link
Copy Markdown
Member

@gantoine gantoine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏼

@gantoine gantoine merged commit 6fe4134 into rommapp:main Feb 1, 2026
@matthew-pye matthew-pye deleted the m3u branch February 1, 2026 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants