3. GraphQL arguments

Querying for a specific track

We've updated our with new s and the Module type, but we still need a way to query for a specific track by its ID. To do that, we'll need to add another entry point to our .

In our schema.js file in the server/src folder, we can see that we only have a single entry point to our API so far: the tracksForHome that returns a list of Track objects. Let's add another one called track, which will return a single Track.

Add the following to our 's Query type:

track: Track
Where can we add entry points to our schema?

We'll be able to specify which unique track we're querying for by giving this an argument.

🤔 How to use GraphQL arguments

An is a value you provide for a particular in your query. The defines the s that each of your s accepts.

Your s can then use a 's provided s to help determine how to populate the data for that . s can help you retrieve specific objects, filter through a set of objects, or even transform the 's returned value. A query that performs a search usually provides the user's search term as an .

Doodle of resolver function retrieving a specific object from data-land using an argument

To define an for a in our , we add parentheses after the name. Inside, we write the name of the followed by a colon, then the type of that , like String or Int. If we have more than one , we can separate them with commas.

Illustration showing the syntax breakdown of using GraphQL arguments
Which of these are reasons to use arguments in a query?

🙌 Using arguments

In our case, we want to use the track's ID as our . Following the syntax rules, we'll add the parentheses, then the name id, with the type ID which is required.

Inside the Query type in schema.js, update the track to:

"Fetch a specific track, provided a track's ID"
track(id: ID!): Track
Code Challenge!

Update the schema below to add two new entry points: 1) Query for a specific spacecat. This field takes an argument id of type non-nullable ID and returns a nullable SpaceCat. 2) Query for a list of missions. This field takes two arguments: to of nullable type String (to specify the mission destination), and scheduled of nullable type Boolean (to filter for scheduled or unscheduled missions). This field returns a nullable array of nullable Missions.

That's it for the query definition. We now have our up-to-date for the feature we're implementing. Onwards to the !


Share your questions and comments about this lesson

Your feedback helps us improve! If you're stuck or confused, let us know and we'll help you out. All comments are public and must follow the Apollo Code of Conduct. Note that comments that have been resolved or addressed may be removed.

You'll need a GitHub account to post below. Don't have one? Post in our Odyssey forum instead.