Run Tasks

[tom-ludwig]

Description

This PR introduces the ability to run tasks within CodeEdit, utilizing a .codeedit folder to store task configurations. The goal is to enable users to create and manage tasks quickly and easily.

Simple Tasks Example:

{
  "tasks" : [
    {
      "command" : "go build",
      "name" : "build",
    }
  ]
}

Tasks with Environment Variables:

  "tasks" : [
    {
      "environmentVariables" : {
        "database" : "maps"
      },
      "target" : "Docker",
      "name" : "build",
      "command" : "go build",
      "workingDirectory" : "\/Users\/tommyludwig\/ScratchFolder\/task-tests"
    }
  ],

Key Structures Introduced:

• CETask: Configuration for executing a task, including command and environment settings.
• CEActiveTask: Represents a running task with output and status (running, stopped, failed, succeeded). CETask is injected into CEActiveTask with essential information such as full command and environment variables.
• CETaskManager: Handles active tasks (run, renew, suspend, resume, terminate, interrupt).
• CEWorkspaceSettings: Holds workspace-specific settings data. Distinct from CEWorkspaceSettingsManager, which handles workspace settings management (e.g., saving, loading).

Active Task States:

An active task can be:

• notRunning: The task hasn't been interacted with yet.
• stopped: The task is currently suspended(paused).
• running: The task is actively running.
• failed: The task finished with an error code.
• finished: The task successfully completed.

Task Shell Options:

TaskShell provides various shells (e.g., bash, zsh, csh) for executing commands. Currently defaults to bash; future updates may include user settings for shell preference. Tasks are executed using executeCommandWithShell, utilizing a Swift Process to run commands within the user's environment plus additional variables from CETask. Output (stdout and stderr) is captured using a Pipe`.

Important

Reviewers, please pay close attention to the usage of classes vs. structs, as well as the naming conventions for classes, functions, and variables. Clear naming decisions now will save significant effort later.

Related Issues

• closes ✨ Tasks (Run scripts in the shell) #262
• closes ✨ Add code compiling support #699

Checklist

• I read and understood the contributing guide as well as the code of conduct
• The issues this PR addresses are related to each other
• My changes generate no new warnings
• My code builds and runs on my machine
• My changes are all related to the related issue above
• I documented my code

Screenshots

[thecoolwinter]

A few visual bugs, and a few possible race conditions with the async methods in CEActiveTask.

[thecoolwinter]

Looking very close to the finish line. Last thing, how should we handle tasks being removed? Right now they stay in the debugger area but I wonder if we should remove them.

And the bottom bar on this list needs a background:

[tom-ludwig]

I’ve taken care of those issues. Over the past few days, I’ve been thinking about how to handle tasks when they get deleted. My initial thought was that active tasks shouldn’t be removed when the run configuration is deleted, as users would lose the task output. However, it might also be really confusing if the active task stays while the configuration disappears. So, I decided to delete the active task if the run configuration is deleted.

[thecoolwinter]

Awesome, I think that's a good decision for the deleted tasks.

Great work!

[0xWDG]

Looks good, you have some conflicts, can you fix those please?

[thecoolwinter]

Should be good to go!