VRETA

GraphQL

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

Two services defining a type with the same name collide when we combine schemas

Nothing forces global uniqueness across the pieces that get stitched together, so a naming collision only surfaces at composition time, often far from whoever wrote either service. Diagnosing which side needs to rename is not obvious from the error alone. We now run a manual check before every schema change goes out.
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.