-
-
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(medusa): Clean response data usage for admin and store fields/expand #3323
Conversation
🦋 Changeset detectedLatest commit: 101076d The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Great work! Only a minuscule todo :)
@adrien2p Don't mind the label here. Added it to later find the PRs that need internal documentation :) |
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.
LGTM 💪
What
The clean response data utils was not properly or easy to use in the context of the admin domain. Cleanup and update the req API to include both
storeAllowedProperties
andadminAllowedProperties
to be used in the appropriate end point handler along side thecleanResponseData
. As of now, the totals fields of any entities will remain present until the todo gets resolved. Otherwise it means that the user need to pass the total fields manually which in the end will trigger the legacy total computation instead of the performant oneRESOLVES CORE-1162