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
Copy file name to clipboardExpand all lines: docs/source/tutorial/schema.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ In our app, we need to provide the following features:
47
47
48
48
We'll use these features to derive the form of queries and mutations our schema needs.
49
49
50
-
* First feature: An example of a query for fetching all upcoming rocket launches would look like:
50
+
***First feature:** An example of a query for fetching all upcoming rocket launches would look like:
51
51
52
52
```js
53
53
{
@@ -59,7 +59,7 @@ We'll use these features to derive the form of queries and mutations our schema
59
59
}
60
60
```
61
61
62
-
* Second feature: An example of a query for a specific launch would look like:
62
+
***Second feature:** An example of a query for a specific launch would look like:
63
63
64
64
```js
65
65
{
@@ -72,7 +72,7 @@ We'll use these features to derive the form of queries and mutations our schema
72
72
73
73
An id is passed to the launch query and the details of the 2nd launch is returned. It could be the first or third or any number specified in the query.
74
74
75
-
From the third feature, we start to deal with users. A query for a signed in user come to mind here and that would look like:
75
+
From the **third feature**, we start to deal with users. A query for a signed in user come to mind here and that would look like:
76
76
77
77
```js
78
78
{
@@ -83,7 +83,7 @@ From the third feature, we start to deal with users. A query for a signed in use
83
83
}
84
84
```
85
85
86
-
Still focusing on the third feature, a user needing to log in seems more than just a query. In most cases, data changes occur such as a new user profile been created because the user doesn't exist. In this case, we're dealing with a `mutation`, which is a special type of query that modifies data.
86
+
Still focusing on the **third feature**, a user needing to log in seems more than just a query. In most cases, data changes occur such as a new user profile been created because the user doesn't exist. In this case, we're dealing with a `mutation`, which is a special type of query that modifies data.
87
87
88
88
```js
89
89
mutation {
@@ -93,7 +93,7 @@ mutation {
93
93
}
94
94
```
95
95
96
-
The fourth feature signifies creation of new data. An example of a mutation would look like:
96
+
The **fourth feature** signifies creation of new data. An example of a mutation for booking a trip would look like:
97
97
98
98
```js
99
99
mutation bookTrip {
@@ -103,7 +103,7 @@ mutation bookTrip {
103
103
}
104
104
```
105
105
106
-
The fifth feature signifies destruction of data. An example of a mutation for this case would look like:
106
+
The **fifth feature** signifies destruction of data. An example of a mutation for cancelling a trip would look like:
0 commit comments