refactor: add type for Final2x-core Config

[Tohrusky]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @Tohrusky, I'm Gemini Code Assist¹! 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 refactors the configuration handling for Final2x-core by introducing a new TypeScript type, Final2xCoreConfig. This change centralizes the configuration structure, improving type safety and clarity across the application, particularly in how configuration is prepared and passed to the core execution command.

Highlights

• New Type Definition: A new TypeScript interface Final2xCoreConfig has been introduced to provide a structured and type-safe representation of the Final2x-core configuration, including both core settings and execution options.
• Unified Configuration Passing: The runCommand function now accepts a single Final2xCoreConfig object, streamlining the API for passing configuration and execution options.
• Configuration Generation Refactor: The utility function responsible for generating the Final2x-core configuration has been renamed from getFinal2xConfig to getFinal2xCoreConfig and updated to return the new typed Final2xCoreConfig object.
• Component Integration Update: The MyProgress.vue component has been updated to utilize the new typed configuration object when invoking the core command.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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. ↩

[gemini-code-assist]

Code Review

This pull request refactors the way configuration is passed from the renderer to the main process by introducing a strongly-typed Final2xCoreConfig object. This is a great improvement for type safety and code clarity. The changes are well-implemented across the affected files. However, a significant issue is the removal of the test file for the configuration generation logic without adding a replacement. It's crucial to restore test coverage for this part of the code.