C# good first issues

AI Summary: This issue describes a bug on Windows 11 where the tooltip for the application's tray icon, specifically within the "hidden icons" overflow area, sometimes fails to disappear after the mouse leaves the icon or the overflow panel is closed. This results in the tooltip lingering on the screen and potentially interfering with other applications.

AI Summary: The default "Contents" headline for the MudPageContentNavigation component is hard-coded in English and is not being translated when the MudBlazor.Translations library is used. This means the headline will appear in English regardless of the runtime language, contrary to the expected behavior of localized text.

AI Summary: This issue seeks native speakers to review and improve existing translations for a game across 14 languages. While all translations are complete, the goal is to refine them for naturalness and accuracy, especially for machine-assisted languages. Contributors can focus on specific sections or languages by submitting small pull requests with JSON file modifications.

AI Summary: The "Select all" text in MudSelect, when `SelectAll` is enabled and `SelectAllText` is not explicitly set, remains hard-coded in English instead of being translated according to the runtime language. This is because the text is currently defined directly in the component's code rather than in the localization resource file.

AI Summary: The Verdict.Async library is missing a `MatchAsync` method, which prevents asynchronous result pipelines from being fully unwrapped asynchronously. This forces developers to materialize the intermediate `Result<T>` into synchronous code, defeating the purpose of the fluent API. The suggested solution is to add `MatchAsync` overloads similar to existing asynchronous extension methods.

AI Summary: This issue proposes adding native ARM64 support for Windows builds. The core change involves a minor modification to the `dotnet publish` command within the `windows.yml` file, along with updates to release artifacts and Winget packaging. Confirmation on ARM64 is required to ensure tray/notification functionality.

AI Summary: This issue requests the addition of a new language translation for the Brink application. It involves copying an existing localization file, translating its content, and updating build scripts and resource directories. The process is outlined in four clear steps, and the issue is marked as a 'good first issue'.

AI Summary: This issue proposes adding an optional menu bar icon that displays the highest-used ring as a percentage. This would be a useful alternative for users who have their screen edges occupied, allowing them to still access ring information via the menu bar. The feature would be opt-in and accessible through a context menu toggle.

AI Summary: This issue requests the addition of a Gemini CLI provider to the Brink tool. The task involves implementing a `UsageProvider` for Gemini CLI, determining its token storage and quota endpoint on different operating systems, and integrating it into the Brink codebase and documentation.

AI Summary: This issue proposes allowing users to choose which display their panel (strip) resides on, rather than being fixed to the main display. It involves adding a context menu option to select a display, persisting this choice, and re-anchoring the panel when screen parameters change. The goal is to improve multi-monitor usability for users who work on external displays.

AI Summary: The user on Windows 11 reports that after minimizing the application to the system tray, the "wheel" (likely a gesture or context menu) becomes unresponsive. They need to reopen the main window to activate it again, despite a prompt indicating background mouse gesture monitoring is active.

AI Summary: This issue proposes adding touch screen input functionality to the ArcadeMaker engine to enable targeting mobile devices. It outlines the steps to implement new engine functions for touch input, mirroring existing mouse and keyboard input patterns, and suggests adding touch event handling as a bonus.

AI Summary: This issue proposes adding a dispatcher to the AutoCleanForm message cleanup process. The goal is to enhance the existing message cleanup functionality by incorporating a dispatcher mechanism, likely for better control or routing of cleanup operations.

AI Summary: This issue proposes adding priority settings to the dispatcher to ensure that form-based messages, such as user form updates, are prioritized. This aims to provide a more responsive and "fluent" UI feeling for users by ensuring critical updates are delivered promptly, even when other message types like newsletters or notifications are also being dispatched.

AI Summary: This feature request asks for "Fix All" support for the xUnit2033 diagnostic in Visual Studio 2022. Currently, the code fix for xUnit2033 can only be applied individually, which is cumbersome when dealing with multiple occurrences during test suite migrations or cleanups. Implementing "Fix All" at document, project, and solution scopes would greatly improve efficiency and consistency.

AI Summary: This issue proposes updating a GitHub Action workflow to use a direct commit hash instead of a tag for the `EndBug/add-and-commit` action. This change is a security improvement, aligning with previous updates made to other actions and workflows.

AI Summary: This issue requests the removal of null characters ('\u0000') from device details, which are currently used for padding. The proposed solution is to apply existing `.Split('\0')` logic to these details to strip the null characters.

AI Summary: This issue requests an improvement to API error messaging, specifically for methods like `.GetDeviceExtendedFormat()`. The current error messages are not granular enough to indicate which parameter or method failed when a `NotifyCommandError` occurs, making debugging more difficult.

AI Summary: The default "Required" error message in MudBlazor components is not being localized when using the MudBlazor.Translations library. The error message remains in English instead of translating to the runtime language, as it is hard-coded in the component's source code.

AI Summary: The GitHub Actions publish workflow incorrectly allows manual dispatches with `dry_run=false` to publish any branch, bypassing the intended tag check. This means un-tagged commits can be pushed to NuGet.org, breaking the workflow's guarantee of versioning via tags.

AI Summary: The CI pipeline collects code coverage data and uploads it to Codecov, but it's configured to never fail the build, even if errors occur during the upload. There are no defined coverage thresholds to enforce a minimum coverage level, rendering the collected data purely decorative and allowing coverage drops to go unnoticed.

AI Summary: The CI pipeline does not compile the examples project because it's not included in the solution file. Additionally, the examples project is marked as packable, which would lead to an unnecessary NuGet package being published if it were included. The fix involves adding the examples project to the solution and marking it as non-packable.

AI Summary: This issue describes a problem where AOT and trimming features are hardcoded to target 'net8.0'. As 'net8.0' approaches end-of-support, adding newer target frameworks like 'net10.0' will result in these features being disabled for those newer frameworks. The proposed fix involves updating the target frameworks and modifying the conditional logic to dynamically include newer versions, ensuring AOT compatibility for future deployments.

AI Summary: This issue proposes standardizing exception handling in controllers to consistently return explicit HTTP status codes (e.g., 500 Internal Server Error) instead of re-throwing exceptions. This will improve predictability for frontends, prevent information leakage, and ensure logging occurs only once. The change involves refactoring existing catch blocks across all controllers and considering more granular exception handling for specific error types.

AI Summary: When publishing a skill that includes a `scripts/` directory, the scripts are not being copied to the published guide's filesystem. This prevents Python tool calls within the skill from accessing these scripts, causing annotation to fail with an `SKILL_PACKAGING` error.

AI Summary: This issue requests the implementation of a Start Menu module for a dock, featuring a Windows icon (or a replaceable icon) that, when clicked, opens the Start Menu. Additionally, the user would like the option to hide the settings module from the dock.

AI Summary: This issue proposes adding support for managing right-click menu items for applications packaged as Microsoft Store apps (AppX/MSIX). These applications, like the desktop version of ChatGPT, do not store their context menu entries in the registry, making them invisible to the current ContextMenuManager tool. The proposed solution involves identifying and managing these entries by parsing the `AppxManifest.xml` file and utilizing the CLSID for blocking.

AI Summary: A bug in the restore functionality causes values within nested structures or array elements of persistent variables to be silently lost, even though the tool reports a successful restore. This issue affects any user restoring structured persistent variables, potentially leading to incorrectly configured plants without any indication of failure.

AI Summary: This issue proposes adding support for PlayStation VR2 controllers to the project. It outlines the various input features of these controllers, including capacitive touch buttons, analog triggers, and joysticks, and notes that integration will be necessary if official support is implemented.

AI Summary: This issue requests the removal of the "New BMP Image" option from the Windows "New" context menu. The user finds this option unnecessary and bothersome, especially since it reappears after Windows updates if the "Paint" application is not uninstalled. They are seeking a way to permanently remove it without constant registry modifications.