Launch at login option for Windows Desktop. #10105
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new abstraction for OS integration and adds support for managing auto-launch settings within the desktop application. It also refactors IPC message handling to use a centralized constants file, improving maintainability and consistency across the codebase. Additionally, new copyright headers are added to several files.
OS Integration & Auto-Launch Feature:
OsIntegrationclass (desktop/src/main/osIntegration.ts) to encapsulate OS-specific features, including tray management and toggling auto-launch settings.Settings, and corresponding unit tests. [1] [2] [3]IPC Message Refactoring:
IpcMessageconstants file (desktop/src/ui/ipcMessages.ts) and refactored all IPC message usages in the main and UI processes to use these constants for better consistency and maintainability. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]Main Process Refactor:
TrayControllerwithOsIntegrationthroughout the main process, including menu actions and badge updates. [1] [2] [3] [4]Copyright and License Headers:
These changes collectively improve the application's extensibility for OS-level features, ensure IPC messaging is robust and maintainable, and establish a foundation for future enhancements.