-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
GraphQL Does Not Reflect Catalog Rule Discounts #39745
Comments
Hi @tuyennn. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-Bravo. Thank you for working on this issue.
|
Hi @tuyennn, Thanks for your reporting and collaboration. We have tried to reproduce the issue in Latest 2.4-develop instance and we are not able to reproduce the issue.Kindly refer the screenshots. Response for Guest Customer ![]() Response for LOGGED in customer ![]() Both are reflecting catalog rule discounts. Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible. Thanks. |
Something wrong with the cache or graphql cache, while triggering save product, the issue is no longer reproducible |
Hi @tuyennn, Thanks for your quick update. Since the issue is no more reproducible we are closing this issue.Please feel free to reopen the issue if the issue still persists. Thanks. |
@engcom-Bravo I believe it was still there but I'm also unable to prove it a valid issue |
Preconditions and environment
Steps to reproduce
Expected result
Response of the price_range from graphql for both scenarios
Actual result
Response for guest customer is ok, but for the logged in customer the response was wrong and doesn't reflect the catalog rule:
Additional information
Well as the investigation, from vendor/magento/module-catalog-rule/etc/webapi_rest/*.xml was not reflected on graphql level should be etc/graphql
Also vendor/magento/module-catalog-rule/etc/events.xml, below content should be applied on graphql level.
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: