NOOP task type: missing from TaskType enum and no builder function
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- api
Research direction
Start with the TaskType enum in src/open-api/types.ts, then inspect the task builders and exports in src/sdk/builders/tasks/index.ts. Add the NOOP builder in src/sdk/builders/tasks/noop.ts and export it so users can create a WorkflowTask with TaskType.NOOP.
Written by the indexing model from the issue text.
Description
Summary
TaskType.NOOP is absent from the TaskType enum in src/open-api/types.ts. There
is no noopTask() builder function. Users cannot create a NOOP workflow task using
the SDK.
NOOP does appear as a string literal in the generated types.gen.ts
(workflowTaskType union) but is not promoted to the TaskType enum.
Server baseline
Conductor 3.32.0-rc.9
Evidence
Static: TaskType enum in types.ts ends at LIST_MCP_TOOLS; no NOOP entry.
Live (2026-07-16): A raw task with "type": "NOOP" was registered and executed
against Conductor OSS 3.32.0-rc.9. The workflow completed successfully — server supports NOOP
fully, the gap is SDK-only.
Proposed fix
Add to TaskType enum in src/open-api/types.ts:
NOOP = "NOOP",
Add builder src/sdk/builders/tasks/noop.ts:
import type { WorkflowTask } from "../../../open-api";
import { TaskType } from "../../../open-api";
export const noopTask = (
taskReferenceName: string,
optional?: boolean
): WorkflowTask => ({
name: taskReferenceName,
taskReferenceName,
type: TaskType.NOOP,
inputParameters: {},
optional,
});
Export from builders/tasks/index.ts.
Related
Discovered during systematic SDK audit against Conductor OSS 3.32.0-rc.9.
Same gap in Java SDK (conductor-oss/java-sdk#130) and Python SDK (conductor-oss/python-sdk#430).
- Dominant language
- TypeScript
- Stars
- 58
- Forks
- 20
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 7
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from conductor-oss/javascript-sdk
-
bug documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
conductor-oss/javascript-sdk#173 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
conductor-oss/javascript-sdk#140 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
conductor-oss/javascript-sdk#139 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 91/100
conductor-oss/javascript-sdk#138 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
conductor-oss/javascript-sdk#137 ·
All issues in conductor-oss/javascript-sdk
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100