chore(orchestration): prevent throwing on already defined workflow (#5337)
**What** At the moment, when importing something from medusa entry point, if two medusa packages are installed because of a plugin, the evaluation of the import can end up throwing that a workflow is already defined. To prevent that from happening, we can just not throw if it is already defined and just return prematurely and make it idempotent.
This commit is contained in:
committed by
GitHub
parent
a1807aea83
commit
e47461d95c
6
.changeset/strong-dragons-flow.md
Normal file
6
.changeset/strong-dragons-flow.md
Normal file
@@ -0,0 +1,6 @@
|
||||
---
|
||||
"@medusajs/orchestration": patch
|
||||
"@medusajs/utilsgst": patch
|
||||
---
|
||||
|
||||
chore(orchestration): prevent throwing on already defined workflow
|
||||
Reference in New Issue
Block a user