GraphQL Schema becomes invalid if a custom `type` product attribute is defined.

[barnard-b]

Preconditions (*)

1. Magento 2.4.3
2. A custom product attribute:
   • Attribute Code: type
   • Default Label: Type
   • Catalog Input Type for Store Owner: Dropdown
   • Values Required: No
   • Manage Options (Values of Your Attribute)
     • Art
     • Books
     • ...
   • Scope: Global
   • Unique Value: No
   • Add to Column Options: No
   • Use in Filter Options: No
   • Use in Search: Yes
   • Visible in Advanced Search: Yes
   • Comparable on Storefront: Yes
   • Use in Layered Navigation: Filterable (with results)
   • Use in Search Results Layered Navigation: Yes
   • Use for Promo Rule Conditions: No
   • Allow HTML Tags on Storefront: Yes
   • Visible on Catalog Pages on Storefront: Yes
   • Used in Product Listing: No
   • Used for Sorting in Product Listing: No

Steps to reproduce (*)

1. Create a custom product attribute as described above in preconditions.
2. Clear the Magento configuration cache to remove the cached GraphQL schema.
3. Open the GraphQL endpoint with a tool that validates the schema like GrapiQL or Apollo Studio.

Expected result (*)

1. The GraphQL schema is valid.

Actual result (*)

1. The schema is invalid because the type attribute on products types has been overwritten with the custom type attribute.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @barnard-b. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 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

[barnard-b]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @barnard-b. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @barnard-b, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[m2-assistant]

Hi @engcom-Echo. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
     Details

     If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[engcom-Echo]

Hi @barnard-b,

Thank you for reporting the issue.

Can you please provide some more info on Point 1 of 'Steps to reproduce' ? Like what are the configurations you set for Attribute Code 'type' ? Bcoz a lot of it is dependent on your configurations which you did while creating new attribute. We'll try to reproduce accordingly.

Thanks

[barnard-b]

@engcom-Echo Attribute configuration has been added. Thanks.

[barnard-b]

@engcom-Echo Is there any more information I should add?