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

# Configuring for CORS
Cross-origin resource sharing **(CORS)** is a mechanism used by browsers and servers that allows resources with certain restrictions to be requested from another location on the web. It does this using a series of `HTTP` headers whose contents lay out a server’s specific rules. These rules detail what resources can be accessed and the way to access them. The default rule for asynchronous JavaScript requests limits access to a same-origin policy. Because our PlateSlate itself isn’t serving up our web application, we need to configure our server to respond to the CORS preflight requests appropriately. This will allow cross-origin requests. Thankfully, there’s a plug for this, named `cors_plug`. We’ll use it directly in our Phoenix endpoint with the default options.

First, let’s add the package to the list of declared dependencies in our PlateSlate `mix.exs`. We should make sure we stop our PlateSlate Elixir application if it’s still running, then install the package using mix:
```
mix deps.get 
```
Once that’s downloaded and ready to go, let’s add the plug to our endpoint. The plug lives under `lib/plate_slate_web`. We’ll put it right after the socket configuration:

Learn about how to configure CORS in plateslate application.

CORS Issue

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

CORS Issue

Configuring for CORS