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

# Organising a schema
Absinthe schemas are compiled.  This means that their types are collected, references are resolved, and the overall structure of the schema is verified against a set of rules. All this happens during Elixir’s module compilation process. Absinthe does this to ensure that GraphQL documents can be processed at runtime using a schema module that’s already been checked for common errors and optimized for better performance. That doesn’t mean our Absinthe schema needs to be written in a single module. In fact, when a schema grows beyond a limited sketch of our domain model into something more comprehensive, it becomes something we need to maintain. To make maintenance easier, it’s a good idea to organize it across multiple modules. To do this, we need something to wire them all together so Absinthe can find the portions of the schema we’ve extracted and organized elsewhere.

Thankfully, Absinthe provides two simple tools to help us: `import_types` and `import_fields`. Let’s look at how we can use these two handy macros in our schema definitions. We can use the PlateSlate example application that we’ve been working on.

## Importing types
All the types referenced in an Absinthe schema are bundled and built into the compiled module during the module compilation process. Right now, in our PlateSlate application, all the types are located inside a single module, `PlateSlateWeb.Schema`. Unfortunately, it’s getting a bit long and unwieldy with each new feature we add.

Let’s consider splitting the custom types from the root type definitions. Since all the types we’ve built so far are `menu-related`, we’ll create a new module, `PlateSlateWeb.Schema.MenuTypes`, to hold them. 

Here’s what that looks like:

Learn how we organize the schema and import the types module in GraphQL.


Schema Organization 

Learn how we organize the schema and import the types module in GraphQL.

Schema Organization

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

Schema Organization

Organising a schema