You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"GraphQL is unapologetically built for front-end engineers, aligning with their way of thinking, how views are structured and how data is consumed.",
15
15
},
16
16
{
17
-
icon: GlobeIcon,
17
+
icon: TournamentIcon,
18
18
title: "Hierarchical",
19
19
description:
20
20
"Most product development involves the creation and manipulation of view hierarchies. GraphQL queries mirror UI structures, ensuring a natural way to request data that matches the shape of the response.",
21
21
},
22
22
{
23
-
icon: CodeIcon,
23
+
icon: ZapIcon,
24
24
title: "Strong-typing",
25
25
description:
26
26
"Every GraphQL service defines a type system, enabling tools to syntactically validate queries before execution and ensuring predictable responses.",
27
27
},
28
28
{
29
-
icon: StarIcon,
29
+
icon: BullseyeIcon,
30
30
title: "Client-specified response",
31
31
description:
32
32
"A GraphQL service publishes the capabilities that its clients are allowed to consume. It is the client who control the data they receive, requesting only what they need at a field level, unlike traditional fixed endpoints.",
33
33
},
34
34
{
35
-
icon: MagnifyingGlassIcon,
35
+
icon: SearchIcon,
36
36
title: "Self-documenting",
37
37
description:
38
38
"GraphQL APIs can describe themselves, allowing tools and clients to query the schema for available types and capabilities. It serves as a powerful platform for building common tools and client software libraries.",
@@ -43,19 +43,19 @@ export function FivePillars() {
0 commit comments