* fix(medusa): sales_channel_id middleware manipulation leading to lost of the sc
* fix(medusa): sales_channel_id middleware manipulation leading to lost of the sc
* add unit tests
* add unit tests
* improve
* integration tests
* docs: fix index.html.md causing 404
* update next.js
* test
* test
* test
* test
* fix revalidate
* test
* test
* test
* test
* test
* test
* test
* test
* clean up
* fix(core-flows): Add more fulfillment data
* fix(core-flows): Add more fulfillment data
* add more fields
---------
Co-authored-by: Riqwan Thamir <rmthamir@gmail.com>
* feat: Add support for uploading a file directly to the file provider from the client
* fix: Add missing types and add a couple of module tests
* fix: Allow nested routes, add test for it
* docs: fix step name in long-running workflow documentation
Fixed inconsistency in the step name - updated 'set-step-failure-step' to 'setStepFailureStep' to match the exported function name.
Fixes#12143
* docs: fix step name in long-running workflow documentation
Changed the step ID from "setStepFailureStep" to "set-step-failure-step" as requested to follow kebab-case naming convention for step IDs.
Fixes#12143
* Update page.mdx
I think this is done. Sorry for inconvenience caused by me.
* Update page.mdx
Sorry for the inconvenience.
* Update page.mdx
Sorry for the inconvenience.
* Update page.mdx
---------
Co-authored-by: Your Name <your-email@example.com>
What:
- Added step config `skipOnPermanentFailure`. Skip all the next steps when the current step fails. If a string is used, the workflow will resume from the given step.
- Fix `continueOnPermanentFailure` to continue the execution of the flow when a step fails.
```ts
createWorkflow("some-workflow", () => {
errorStep().config({
skipOnPermanentFailure: true,
})
nextStep1() // skipped
nextStep2() // skipped
})
createWorkflow("some-workflow", () => {
errorStep().config({
skipOnPermanentFailure: "resume-from-here",
});
nextStep1(); // skipped
nextStep2(); // skipped
nextStep3().config({ name: "resume-from-here" }); // executed
nextStep4(); // executed
});
```
**What**
Now that all events management are fixed in the workflows life cycle, the run as step needs to leverage the workflow engine if present (which should always be the case for async workflows) in order to ensure the continuation and the ability to mark parent step in parent workflow as success or failure
Co-authored-by: Carlos R. L. Rodrigues <37986729+carlos-r-l-rodrigues@users.noreply.github.com>
**What**
- custom setting routes were registered under `/settings/settings/custom-route` instead of `/settings/custom-route`
---
CLOSES SUP-1384
Co-authored-by: Oli Juhl <59018053+olivermrbl@users.noreply.github.com>
The `application_method_type` filter has a `string` type in the HTTP types. This PR accurately sets the type. This is useful for the generated OAS to show the possible filter values.
