8c17396285
This commit improves the management of script execution process by enhancing the way terminal commands are handled, paving the way for easier future modifications and providing clearer feedback to users when scripts are cancelled. Previously, the UI displayed a generic error message which could lead to confusion if the user intentionally cancelled the script execution. Now, a specific error dialog will appear, improving the user experience by accurately reflecting the action taken by the user. This change affects code execution on Linux where closing GNOME terminal returns exit code `137` which is then treated by script cancellation by privacy.sexy to show the accurate error dialog. It does not affect macOS and Windows as curret commands result in success (`0`) exit code on cancellation. Additionally, this update encapsulates OS-specific logic into dedicated classes, promoting better separation of concerns and increasing the modularity of the codebase. This makes it simpler to maintain and extend the application. Key changes: - Display a specific error message for script cancellations. - Refactor command execution into dedicated classes. - Improve file permission setting flexibility and avoid setting file permissions on Windows as it's not required to execute files. - Introduce more granular error types for script execution. - Increase logging for shell commands to aid in debugging. - Expand test coverage to ensure reliability. - Fix error dialogs not showing the error messages due to incorrect propagation of errors. Other supported changes: - Update `SECURITY.md` with details on script readback and verification. - Fix a typo in `IpcRegistration.spec.ts`. - Document antivirus scans in `desktop-vs-web-features.md`.
58 lines
2.0 KiB
TypeScript
58 lines
2.0 KiB
TypeScript
import { join } from 'node:path';
|
|
import { chmod, mkdir } from 'node:fs/promises';
|
|
import { exec } from 'node:child_process';
|
|
import { app } from 'electron/main';
|
|
import type {
|
|
CommandOps, FileSystemOps, LocationOps, OperatingSystemOps, SystemOperations,
|
|
} from './SystemOperations';
|
|
|
|
/**
|
|
* Thin wrapper for Node and Electron APIs.
|
|
*/
|
|
export class NodeElectronSystemOperations implements SystemOperations {
|
|
public readonly operatingSystem: OperatingSystemOps = {
|
|
/*
|
|
This method returns the directory for storing app's configuration files.
|
|
It appends your app's name to the default appData directory.
|
|
Conventionally, you should store user data files in this directory.
|
|
However, avoid writing large files here as some environments might back up this directory
|
|
to cloud storage, potentially causing issues with file size.
|
|
|
|
Based on tests it returns:
|
|
|
|
- Windows: `%APPDATA%\privacy.sexy`
|
|
- Linux: `$HOME/.config/privacy.sexy/runs`
|
|
- macOS: `$HOME/Library/Application Support/privacy.sexy/runs`
|
|
|
|
For more details, refer to the Electron documentation: https://web.archive.org/web/20240104154857/https://www.electronjs.org/docs/latest/api/app#appgetpathname
|
|
*/
|
|
getUserDataDirectory: () => {
|
|
return app.getPath('userData');
|
|
},
|
|
};
|
|
|
|
public readonly location: LocationOps = {
|
|
combinePaths: (...pathSegments) => join(...pathSegments),
|
|
};
|
|
|
|
public readonly fileSystem: FileSystemOps = {
|
|
setFilePermissions: (
|
|
filePath: string,
|
|
mode: string | number,
|
|
) => chmod(filePath, mode),
|
|
createDirectory: async (
|
|
directoryPath: string,
|
|
isRecursive?: boolean,
|
|
) => {
|
|
await mkdir(directoryPath, { recursive: isRecursive });
|
|
// Ignoring the return value from `mkdir`, which is the first directory created
|
|
// when `recursive` is true, or empty return value.
|
|
// See https://github.com/nodejs/node/pull/31530
|
|
},
|
|
};
|
|
|
|
public readonly command: CommandOps = {
|
|
exec,
|
|
};
|
|
}
|