ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #graphql
Goal and Context We need to verify that Apollo Server correctly reports @deprecated fields during introspection, especially across recent releases. The GraphQL specification mandates that a deprecated field must expose isDeprecated: true and a deprecationReason string via the __type introspection system. Historically, Apollo Server 2.x adhered to this contra
Integration boundary We are exposing order data from Magento 2.x through the native GraphQL API to a headless storefront. Date fields such as created_at come back as UTC ISO 8601 strings, while the store view is configured with a regional timezone under Stores > Configuration > General > Locale Options. The storefront must display order times in the
REST API vs GraphQL: Balancing Simplicity and Flexibility for Zero‑Downtime Migration The goal is to transition a lightweight Java application that currently relies on Trello’s REST API v2 to a zero‑downtime deployment while evaluating the feasibility of adopting the newer GraphQL API. The migration must preserve continuous availability, handle OAuth 2.0 aut
Goal: Diagnose what HTTP status code and response body a GraphQL server should return when a client submits a persisted query ID that is missing from the server registry. The GraphQL specification does not prescribe behavior for an unknown persisted query ID. Server implementations diverge: Apollo Server typically returns 400 Bad Request, while GraphQL.js ma
The goal is to determine whether a custom @accessible directive can be used to attach accessibility information (such as ARIA roles or labels) to GraphQL fields and have that information survive introspection and error‑payload generation in Apollo Server 4. Because the GraphQL specification does not standardize accessibility metadata, servers may ignore unkn
magento
trello