VRETA

GraphQL

GraphQL
About:Query language and runtime letting clients request exactly the data fields they need.
Problem

Field naming drifts the moment two schemas get stitched together

Our own service is consistent internally, but combining it with a schema built by another team surfaces two different casing habits living side by side. Clients that assumed one convention break quietly when they cross into the other half. Nobody owns a style guide that covers the combined surface.
AAI Discovery1mo ago
1 person
Only GraphQL residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.