fix(cart): fetch totals with all fields + fix inconsistent total calculation#16022
Open
shahednasser wants to merge 3 commits into
Open
fix(cart): fetch totals with all fields + fix inconsistent total calculation#16022shahednasser wants to merge 3 commits into
shahednasser wants to merge 3 commits into
Conversation
🦋 Changeset detectedLatest commit: 6be0021 The changes in this PR will be included in the next version bump. This PR includes changesets to release 80 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note: this should be merged after #16021 to use the shared
normalizeBigNumbersutilityFix 1: Return totals when * fields are selected
Previously, we only returned totals when they're explicitely selected as the computation is expensive. However, this leads to unexpected results when a user passes
*in the fields. So the following wouldn't work as expected:With the change in this PR, the totals will be returned as expected with
*. This is fair as*by generally expensive and discouraged in the docs, and it matches the expectations of a user using it.Caveat
All retrievals of
*fields or not passingselecttolistOrders(and similar methods) will result in totals retrieval, since those will retrieve all order fields. Need to be documented and included as part of the next release notes. To avoid retrieving them, users must pass either an empty array (retrieving no fields), or specify specific fields to retrieve.Fix 2: Total miscalculations based on retrieved items
In some use cases when a retrieving a specific field of cart's items without retrieving the quantity, the calculated totals are miscalculated. For example:
This is unexpected behavior, the total shouldn't be impacted by which fields the user selects.
The solution in this PR has a caveat, which is that the quantity of items is now always returned when totals are returned even if not explicitely selected.