VRETA

GraphQL

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

There is no agreed way to retire a field and every team does it differently

One team marks a field deprecated and leaves it forever, another removes it on a deadline nobody was told about. Clients built against the old shape break without warning because deprecation carries no enforcement. We have started keeping our own internal changelog since the schema does not tell that story.
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.