Open griest024 opened 2 months ago
Hi @griest024. Thank you for your report. To speed up processing of this issue, 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:
@magento give me 2.4-develop instance
- upcoming 2.4.x release@magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: 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.
@magento give me 2.4-develop instance
Hi @griest024. Thank you for your request. I'm working on Magento instance for you.
Hi @griest024, here is your Magento Instance: https://d20bcd2a6e2531fad2efc882e1a1a3eb.instances-prod.magento-community.engineering Admin access: https://d20bcd2a6e2531fad2efc882e1a1a3eb.instances-prod.magento-community.engineering/admin_453f Login: 7eb7b20f Password: 4754edd6aec4
reproed on the 2.4-develop instance
Hi @engcom-Dash. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Hi @engcom-Delta. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. Hi @griest024 ,
Verified the issue on 2.4-develop and it is reproducible.
Hence, Confirming the issue.
Steps to reproduce:-
1.go to graphql 2.Send a GraphQL request with deeply (>1) nested GraphQL fragments
:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-12316 is successfully created for this GitHub issue.
:white_check_mark: Confirmed by @engcom-Delta. Thank you for verifying the issue.
Issue Available: @engcom-Delta, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
@engcom-Delta As per discussion in the triage call please rework this issue. Till the time moving it to Ready for confirmation
.
Thanks
Hi @griest024 ,
Thanks for your reporting and collaboration. We have verified the issue in latest 2.4-develop instance and it is reproducible.
Hence, Confirming the issue.
Steps to reproduce:-
1.Go to graphql 2.Run GraphQL request with deeply (>1) nested GraphQL fragments
:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-12316
Preconditions and environment
Magento version: 2.4.6-p6
Steps to reproduce
Send a GraphQL request with the following query:
and the following variables:
Expected result
Actual result
Additional information
This is almost certainly related to #31086.
Any of the following causes
name
to be filled with the correct data:name
field selection to thedepth0
fragment:name
field selection to the body of the query:name
to the selection set of thechildren
(why?????):Its interesting that some fields can be selected in deeply nested fragments, such as
uid
. The following query gives the correct value foruid
:Release note
No response
Triage and priority