conductor-oss / conductor-oss/javascript-sdk
NOOP task type: missing from TaskType enum and no builder function
- Langage dominant
- TypeScript
- Étoiles
- 58
- Forks
- 20
- Merge moyen
- 1 j 13 h
- PR mergées (30 j)
- 7
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`:
```typescript
NOOP = "NOOP",
```
Add builder `src/sdk/builders/tasks/noop.ts`:
```typescript
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).
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- typescript
- Domaine
- api
- Type d'issue
- Bug
- Difficulté
- 2/5
- Temps estimé
- 1-3 heures
- Activité
- Calme
- Clarté
- Clairement spécifiée
- Accessibilité débutants
- 88/100