You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue Description:
We encountered an issue while utilizing an API platform test template to create a class. Initially, the class incorporated both REST and GraphQL operations, as demonstrated below:
Understanding that our application purely relies on GraphQL operations, we decided to eliminate the REST annotations, leaving only the GraphQL-related ones:
Encountered Issue:
Post adjustments, fetching a single instance through GraphQL operation results in an error. The error indicates an issue tied to the Query provider being unrecognized, despite its explicit definition. This behavior is counterintuitive since removing the 'Query' operation should inhibit GraphQL operations, yet specifying it leads to provider-related errors.
Expected Behavior:
The system should seamlessly fetch a single entity or a collection based on GraphQL operations without necessitating the definition of REST-oriented providers (Get and GetCollection), especially when our usage context exclusively involves GraphQL.
Actual Behavior:
When attempting to fetch a single entity via GraphQL, the system fails, suggesting that a 'Get' provider is mandatory despite the active 'Query' provider. This not only contradicts the expected behavior but also limits our operations strictly to GraphQL, complicating the implementation process.
Steps to Reproduce:
Create a class using the provided API platform test template.
This issue suggests a potential misunderstanding or misconfiguration in handling GraphQL operations within the system, necessitating a closer examination and resolution to align with the anticipated outcome.
Post scriptum:
When Get related annotations are defined, everything functions as intended. However, an issue arises upon solely relying on GraphQL operations after removing REST-specific annotations (Get, GetCollection). This leads to an unexpected error when fetching a single entity using GraphQL, pointing to a discrepancy between expected and actual behavior concerning operation providers.
The text was updated successfully, but these errors were encountered:
API Platform version(s) affected: 3.2.16
Bug Report
Issue Description:
We encountered an issue while utilizing an API platform test template to create a class. Initially, the class incorporated both REST and GraphQL operations, as demonstrated below:
Understanding that our application purely relies on GraphQL operations, we decided to eliminate the REST annotations, leaving only the GraphQL-related ones:
Encountered Issue:
Post adjustments, fetching a single instance through GraphQL operation results in an error. The error indicates an issue tied to the Query provider being unrecognized, despite its explicit definition. This behavior is counterintuitive since removing the 'Query' operation should inhibit GraphQL operations, yet specifying it leads to provider-related errors.
Expected Behavior:
The system should seamlessly fetch a single entity or a collection based on GraphQL operations without necessitating the definition of REST-oriented providers (
Get
andGetCollection
), especially when our usage context exclusively involves GraphQL.Actual Behavior:
When attempting to fetch a single entity via GraphQL, the system fails, suggesting that a 'Get' provider is mandatory despite the active 'Query' provider. This not only contradicts the expected behavior but also limits our operations strictly to GraphQL, complicating the implementation process.
Steps to Reproduce:
Get
,GetCollection
).Error Encountered:
This issue suggests a potential misunderstanding or misconfiguration in handling GraphQL operations within the system, necessitating a closer examination and resolution to align with the anticipated outcome.
Post scriptum:
When
Get
related annotations are defined, everything functions as intended. However, an issue arises upon solely relying on GraphQL operations after removing REST-specific annotations (Get
,GetCollection
). This leads to an unexpected error when fetching a single entity using GraphQL, pointing to a discrepancy between expected and actual behavior concerning operation providers.The text was updated successfully, but these errors were encountered: