commandsv3/CommandsV3.json

{
  "fileName": "CommandsV3.json",
  "name": "Commands v3",
  "version": "1.0.0",
  "uuid": "4decdc05-a056-46cf-9561-39449bbb0130",
  "frcYear": "2027_alpha1",
  "mavenUrls": [],
  "jsonUrl": "",
  "javaDependencies": [
    {
      "groupId": "org.wpilib",
      "artifactId": "commands3-java",
      "version": "wpilib"
    }
  ],
  "jniDependencies": [],
  "cppDependencies": []
}
[commands] Add Commands v3 framework (#6518) The framework fundamentally relies on the continuation API added in Java 21 (which is currently internal to the JDK). Continuations allow for call stacks to be saved to the heap and resumed later. The async framework allows command bodies to be written in an imperative style. However, an async command will need to be actively cooperative and periodically call coroutine.yield() in loops to yield control back to the command scheduler to let it process other commands. There are also some other additions like priority levels (as opposed to a blanket yes/no for ignoring incoming commands), factories requiring names be provided for commands, and the scheduler tracking all running commands and not just the highest-level groups. However, those changes aren't unique to an async framework, and could just as easily be used in a traditional command framework. 2025-10-10 16:47:22 -04:00			`{`
			`"fileName": "CommandsV3.json",`
			`"name": "Commands v3",`
			`"version": "1.0.0",`
			`"uuid": "4decdc05-a056-46cf-9561-39449bbb0130",`
			`"frcYear": "2027_alpha1",`
			`"mavenUrls": [],`
			`"jsonUrl": "",`
			`"javaDependencies": [`
			`{`
[cmd3] Correct the groupId for commands v3 in the JSON (#8306) 2025-10-26 00:08:42 -07:00			`"groupId": "org.wpilib",`
[commands] Add Commands v3 framework (#6518) The framework fundamentally relies on the continuation API added in Java 21 (which is currently internal to the JDK). Continuations allow for call stacks to be saved to the heap and resumed later. The async framework allows command bodies to be written in an imperative style. However, an async command will need to be actively cooperative and periodically call coroutine.yield() in loops to yield control back to the command scheduler to let it process other commands. There are also some other additions like priority levels (as opposed to a blanket yes/no for ignoring incoming commands), factories requiring names be provided for commands, and the scheduler tracking all running commands and not just the highest-level groups. However, those changes aren't unique to an async framework, and could just as easily be used in a traditional command framework. 2025-10-10 16:47:22 -04:00			`"artifactId": "commands3-java",`
			`"version": "wpilib"`
			`}`
			`],`
			`"jniDependencies": [],`
			`"cppDependencies": []`
			`}`