Use correct base price in PricingResponse #2080
Open
+1
−1
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.
Base price shouldn't be customerGroup scoped, so use $basePrice where customer_group_id is false.
The basePrice is initially retrieved correctly:
lunar/packages/core/src/Managers/PricingManager.php
Line 198 in 467b497
then is not used in PricingResponse, instead is newly retrieved loosing the condition that customer_group_id must be false.
lunar/packages/core/src/Managers/PricingManager.php
Line 220 in 467b497
That makes potentially get the wrong price as basePrice