Gain insights into crafting GraphQL APIs with Elixir's Absinthe. Explore building schemata, securing endpoints, and integrating frontends to master creating, publishing, and utilizing robust GraphQL APIs.

Craft GraphQL APIs in Elixir with Absinthe.png

graphql.tar.gz

Chapter_2_1_start

Chapter_2_2_object_Running_GraphQLServer

Chapter_2_2_object

Chapter_3_3_matching

Chapter_3_3_matching_GraphQiL

Chapter_4_2_Union_GraphQiL

Chapter_5_2_Create

Chapter_6_4-publish

Chapter_6_4-orderingapi

Chapter_7_5-default

Chapter_8_2-login

Chapter_8_3-context

Chapter_9_dataloader

Chapter_10_Start

Chapter_10_2_action

Chapter_10_3_put

Chapter_10_4_login

Chapter_10_5_History

Chapter_11_2_subsription

Chapter_11_1_start

Chapter_11_hybird

Chapter_11_Applo_Client

Chapter_11_1_start-Updated

Chapter11-2-HTTP-Subscription

Chapter11-2-HTTP-Relay-Subscription

GraphQL is an API query language that allows clients to ask for exactly what they need and nothing more makes it easier to evolve APIs over time.

This course is divided into three parts, Part 1- Build a GraphQL API, Part 2- Publish Your API, and Part-3 Use Your API. 

In the first part, you will cover topics ranging from basic GraphQL, Building GraphQL Schema, Taking User Input, Adding Flexibility, Making a Change with Mutations, and Going Live with Subscriptions.

In the second part, you will cover topics ranging from Resolution Middleware, Securing with Authentication and Authorization, and Tuning Resolution.

The third part will cover topics ranging from Driving Phoenix Actions with GraphQL, Integrating with the Frontend and GraphQL Types. Upon completing this course, you will have sufficient foundational knowledge of GraphQL, and you can build, publish and use your API in GraphQL.

Craft GraphQL APIs in Elixir with Absinthe

# Defining field arguments

GraphQL documents are made up of fields. The user lists the fields they would like, and the schema uses its definition of those fields to resolve the pieces of data that match. However, the system would be inflexible if it did not allow users to provide additional parameters to clarify exactly what information each field needs to find. A user requesting information about `menuItems`, for instance, may want to see certain menu items or a certain number of them. For this reason, GraphQL has the concept of **field arguments**, which are defined as "a way for users to provide input to fields that can be used to parameterize their queries."

Let's look at our example application and see how we can extend our Absinthe schema by defining the arguments our API will accept for a field. Then, we can see how we can use those arguments to tailor the result for users.

We’ve already built a field in the [schema.ex](https://www.educative.io/courses/craft-graphql-api-elixir-absinthe/adding-fields-in-graphql-schema) file of our API, but we could make it more flexible. To do so, we'll accept user input, which in this case is the list of menu items. Our schema’s `menuItems` field looks something like this:

 

 Learn defining field arguments for GraphQL.


Field Arguments

Learn defining field arguments for GraphQL.

Getting Started

Meet GraphQL

Building Schema of GraphQL

Taking User Input

Adding Flexibility

Making a Change with Mutations

Going Live with Subscriptions

Resolution Middleware

Securing with Authentication and Authorization

Tuning Resolution

Driving Phoenix Actions with GraphQL

Integrating with the Front-end

Conclusion

Field Arguments

Defining field arguments