-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
fix(order,utils): fix outstanding amount stuck on long orders #8968
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
6 Skipped Deployments
|
|
@@ -304,7 +304,7 @@ export function MedusaInternalService< | |||
if (keySelectorForDataOnly.$or.length) { | |||
const entitiesToUpdate = await this.list( | |||
keySelectorForDataOnly, | |||
{}, | |||
{ take: null }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc. @adrien2p just so you are aware
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we pass the selector to mikro orm instead of listing first?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought we fixed that long time ago 😅
what:
When update requests cross the default limit, it doesn't update any records beyond it. This PR fixes the issue generally on the abstract internal service and additionally for the order module when sub-resources cross the default limit.
RESOLVES CC-367