feat(workflows-sdk): Allow a step to not define an expected input (#5775)

**What**
Allow a step to not define an expected input, previously even if no input was expected, an object was always expected to be passed to the stepFunction inside the workflow composition. Now
```ts
const stepWithoutArgs = createStep("step1", () => {
  return new StepResponse("string")
})

const stepWithoutExepectedInput = createStep("step2", (_: {}, context) => {
  console.log("input", _) // {}
  return new StepResponse("string")
})

const workflow = createWorkflow("workflow1", () => {
  stepWithoutArgs()
  return stepWithoutExepectedInput()
})

workflow()
  .run()
  .then((res) => {
    console.log(res.result) // string
  })
```

This commit is contained in:

Adrien de Peretti

2023-12-21 13:41:58 +00:00

committed by

GitHub

parent 890e76a5c5

commit 8402f46970

5 changed files with 73 additions and 21 deletions

									
										.changeset/hip-turtles-smell.md
									
		+5
		
												View File
												
				@@ -0,0 +1,5 @@

				---

				"@medusajs/workflows-sdk": patch

				---

				feat(workflows-sdk): Allow a step to not define an expected input