Skip to content

Commit 13816d9

Browse files
authored
Fix wrong meaning in "thinking in graphs - legacy" (#917)
I think the how and what should be swapped here, since it doens's make much sense based on the previous phrase.
1 parent 5c02d22 commit 13816d9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/learn/BestPractice-ThinkingInGraphs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ In the diagram above, all entry points (REST, GraphQL, and RPC) into the system
6464
6565
Sometimes, you will find yourself working with legacy data sources that do not perfectly reflect how clients consume the data. In these cases, prefer building a GraphQL schema that describes how clients use the data, rather than mirroring the legacy database schema.
6666

67-
Build your GraphQL schema to express "what" rather than "how". Then you can improve your implementation details without breaking the interface with older clients.
67+
Build your GraphQL schema to express "how" rather than "what". Then you can improve your implementation details without breaking the interface with older clients.
6868

6969
## One Step at a time
7070
> Get validation and feedback more frequently

0 commit comments

Comments
 (0)