If someone creates an appium task and runs it, the tree should know about this and create a transient tree item (a configuration which is not bound to an .appiumserver file).

The user should be able to save this file to persist the setting (so it will show the server as "offline" when not running). This would be a new UI element somewhere.

Do not create a new file to do this unless there's no other way to do it.

I am not sure if these are working right now. But we should make it work and add a GH action to run it.

We may or may not want webdriverio to automate a local server. But to fully test everything, the Appium server needs to have active sessions. I have had some success with webdriverio/appium-boilerplate for config (and there may be some stubs hanging around). Using fake-driver may make more sense than trying to run an android or iOS emulator in CI though, since driver behavior is really out of scope (for now)...

1. When the extensions's configuration changes, the extension should react accordingly.
2. For example, if the server polling interval is adjusted, the extension should make an adjustment.
3. ConfigService has some weird bespoke thing I wrote before I fully grokked vscode.Event, so remove that and replace it with vscode.Event.

Determine what exactly needs to happen when x changes. I should probably do this.

Get logs for a session in the tree

Some people don't like this, but I do.

• add lint-staged and husky to run a precommit hook which calls eslint --fix
• configure eslint to work with the prettier plugin (so that eslint reports formatting issues, and eslint --fix formats via prettier)
• ensure .ts, .d.ts, .js, .mjs, .md and .json files are formatted
• do not format package-lock.json or package.json
• run prettier on CHANGELOG.md after standard-version updates it, but before standard-version commits it (and make sure it's staged).

This would be a good task for someone who knows about this sort of configuration but otherwise doesn't know much about Appium or VS Code extensions.

This extension has to bundle Appium, but Appium is like 30MB of stuff (at least).
Attempting to bundle it using esbuild was met with failure (love those dynamic requires), but someone might get it to work if they keep trying. It would still be a couple MB, minified.

The extension may be able to actually just go download and install Appium into its storage directory if it is needed. e.g. if someone wants to run a local server but doesn't have Appium installed--automatically download and install it.

You know how you can click the button at the top of the editor in VSCode Settings view to open settings.json? Like that.