<< Prev Question Next Question >>
Question 19/25
An external system integrates functionality of a product catalog search using Adobe Commerce GraphQL API.
The Architect creates a new attribute my_attribute in the admin panel with frontend type select-Later, the Architect sees that Productlnterf ace already has the field my_attribute, but returns an Int value. The Architect wants this field to be a new type that contains both option id and label.
To meet this requirement, an Adobe Commerce Architect creates a new module and file etc/schema.graphqls that declares as follows:
After calling command setup:upgrade, the introspection of Productlnterface field my_attribute remains Int.
What prevented the value type of field my_attribute from changing?
The Architect creates a new attribute my_attribute in the admin panel with frontend type select-Later, the Architect sees that Productlnterf ace already has the field my_attribute, but returns an Int value. The Architect wants this field to be a new type that contains both option id and label.
To meet this requirement, an Adobe Commerce Architect creates a new module and file etc/schema.graphqls that declares as follows:
After calling command setup:upgrade, the introspection of Productlnterface field my_attribute remains Int.
What prevented the value type of field my_attribute from changing?
