xampp-panel@backids99: Add MySQL shortcuts

[GabrielCamara3526]

• Add MySQL Server actions
• Add new applet structure of code
• Add switch option to settings schema
• Notify user on operations
• Remove last edited metadata key

[github-actions]

Best-practices scanner

This is a regex-based check for API usage that can pose security, performance or
maintainability issues, or that may already be provided by Cinnamon. Having code flagged
by it doesn't automatically disqualify a pull request.

This check is not perfect will not replace a normal review.

---

Found 10 potential issue(s):

ℹ️ shell_string_spawn

xampp-panel@backids99/files/xampp-panel@backids99/applet.js:59

Util.spawnCommandLineAsync(CommandConstants.COMMAND_START_LINUX_MANAGER, null, null);

Prefer argument vector spawn functions over shell command strings.
This is especially important when arguments include untrusted input (user data,
filenames, settings values, etc.) as shell strings are vulnerable to injection.
Static command strings are generally fine, but argv is always safer.
Use Util.spawn(["cmd", "arg1", "arg2"]) or Util.trySpawn() instead.

xampp-panel@backids99/files/xampp-panel@backids99/applet.js:62

Util.spawnCommandLineAsync(CommandConstants.COMMAND_START_XAMPP, null, null);

Prefer argument vector spawn functions over shell command strings.
This is especially important when arguments include untrusted input (user data,
filenames, settings values, etc.) as shell strings are vulnerable to injection.
Static command strings are generally fine, but argv is always safer.
Use Util.spawn(["cmd", "arg1", "arg2"]) or Util.trySpawn() instead.

xampp-panel@backids99/files/xampp-panel@backids99/applet.js:65

Util.spawnCommandLineAsync(CommandConstants.COMMAND_STOP_XAMPP, null, null);

Prefer argument vector spawn functions over shell command strings.
This is especially important when arguments include untrusted input (user data,
filenames, settings values, etc.) as shell strings are vulnerable to injection.
Static command strings are generally fine, but argv is always safer.
Use Util.spawn(["cmd", "arg1", "arg2"]) or Util.trySpawn() instead.

xampp-panel@backids99/files/xampp-panel@backids99/applet.js:68

Util.spawnCommandLineAsync(CommandConstants.COMMAND_RESTART_XAMPP, null, null);

Prefer argument vector spawn functions over shell command strings.
This is especially important when arguments include untrusted input (user data,
filenames, settings values, etc.) as shell strings are vulnerable to injection.
Static command strings are generally fine, but argv is always safer.
Use Util.spawn(["cmd", "arg1", "arg2"]) or Util.trySpawn() instead.

xampp-panel@backids99/files/xampp-panel@backids99/applet.js:75

Util.spawnCommandLineAsync(CommandConstants.COMMAND_START_MYSQL, () => {

Prefer argument vector spawn functions over shell command strings.
This is especially important when arguments include untrusted input (user data,
filenames, settings values, etc.) as shell strings are vulnerable to injection.
Static command strings are generally fine, but argv is always safer.
Use Util.spawn(["cmd", "arg1", "arg2"]) or Util.trySpawn() instead.

xampp-panel@backids99/files/xampp-panel@backids99/applet.js:80

Util.spawnCommandLineAsync(CommandConstants.COMMAND_STOP_MYSQL, () => {

Prefer argument vector spawn functions over shell command strings.
This is especially important when arguments include untrusted input (user data,
filenames, settings values, etc.) as shell strings are vulnerable to injection.
Static command strings are generally fine, but argv is always safer.
Use Util.spawn(["cmd", "arg1", "arg2"]) or Util.trySpawn() instead.

xampp-panel@backids99/files/xampp-panel@backids99/applet.js:85

Util.spawnCommandLineAsync(CommandConstants.COMMAND_RESTART_MYSQL, () => {

Prefer argument vector spawn functions over shell command strings.
This is especially important when arguments include untrusted input (user data,
filenames, settings values, etc.) as shell strings are vulnerable to injection.
Static command strings are generally fine, but argv is always safer.
Use Util.spawn(["cmd", "arg1", "arg2"]) or Util.trySpawn() instead.

xampp-panel@backids99/files/xampp-panel@backids99/applet.js:93

Util.spawnCommandLine(CommandConstants.COMMAND_OPEN_WEBDIR);

Prefer argument vector spawn functions over shell command strings.
This is especially important when arguments include untrusted input (user data,
filenames, settings values, etc.) as shell strings are vulnerable to injection.
Static command strings are generally fine, but argv is always safer.
Use Util.spawn(["cmd", "arg1", "arg2"]) or Util.trySpawn() instead.

xampp-panel@backids99/files/xampp-panel@backids99/applet.js:96

Util.spawnCommandLine(CommandConstants.COMMAND_LAUNCH_WEBDIR);

Prefer argument vector spawn functions over shell command strings.
This is especially important when arguments include untrusted input (user data,
filenames, settings values, etc.) as shell strings are vulnerable to injection.
Static command strings are generally fine, but argv is always safer.
Use Util.spawn(["cmd", "arg1", "arg2"]) or Util.trySpawn() instead.

xampp-panel@backids99/files/xampp-panel@backids99/applet.js:99

Util.spawnCommandLine(CommandConstants.COMMAND_LAUNCH_PHPMYADMIN);

Prefer argument vector spawn functions over shell command strings.
This is especially important when arguments include untrusted input (user data,
filenames, settings values, etc.) as shell strings are vulnerable to injection.
Static command strings are generally fine, but argv is always safer.
Use Util.spawn(["cmd", "arg1", "arg2"]) or Util.trySpawn() instead.

---

Automated pattern check.