-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
feat: wire up direct uploads with local file provider #12643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
bd9e721
a4bf4dc
961a8ca
f8acc5a
7830dbf
51ead6c
291b981
dcbca95
ebd85d9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
--- | ||
"@medusajs/file-local": patch | ||
"@medusajs/core-flows": patch | ||
"@medusajs/js-sdk": patch | ||
"@medusajs/dashboard": patch | ||
"integration-tests-http": patch | ||
--- | ||
|
||
feat: wire up direct uploads with local file provider |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -12,7 +12,10 @@ export const processImportChunksStepId = "process-import-chunks" | |
* const data = parseProductCsvStep("products.csv") | ||
*/ | ||
export const processImportChunksStep = createStep( | ||
processImportChunksStepId, | ||
{ | ||
name: processImportChunksStepId, | ||
async: true, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If I do not convert this step to @carlos-r-l-rodrigues can you confirm if my assumption is correct? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. When composing the workflow, as the step to wait for confirmation is async, this workflow will be automatically flagged as async. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Okay. But I noticed that without this flag, the endpoint waits for the workflow to finish. Maybe what I need is There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Btw, I have been following this guide https://docs.medusajs.com/learn/fundamentals/workflows/long-running-workflow There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
This shouldn't happen. When there is one async step, the worklfow.run will return as soon as it get to this step. When that step is finished, it will continue in another process. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. programatically speaking, we do not await when we execute an async step. if you want we can take a look together to be sure of what is happening |
||
}, | ||
async (input: { chunks: { id: string }[] }, { container }) => { | ||
const file = container.resolve(Modules.FILE) | ||
|
||
|
Uh oh!
There was an error while loading. Please reload this page.