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: BundleItemOption is missing price_range
#35010
Comments
Hi @damienwebdev. Thank you for your report.
Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
For more details, review the Magento Contributor Assistant documentation. Add a comment to assign the issue: To learn more about issue processing workflow, refer to the Code Contributions.
🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
I don't think this is a feature request, but missed requirements preventing bundle product rendering |
Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Once all required labels are present, please add |
Hi @damienwebdev , Kindly upgrade to the latest Magento version In case of any Magento related issues found in For any Magento related references, you may refer to the Magento user guide. Thanks! |
Description (*)
Unlike the rest of the pricing API, the GraphQl type
BundleItemOption
is missing aprice_range
.Expected behavior (*)
I can query the
price_range
of aBundleItemOption
Benefits
Price consistency across the API.
The text was updated successfully, but these errors were encountered: