<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>absinthe on Washington Botelho</title><link>http://www.wbotelhos.com/tags/absinthe/</link><description>Recent content in absinthe on Washington Botelho</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 24 Aug 2021 00:00:00 -0300</lastBuildDate><atom:link href="http://www.wbotelhos.com/tags/absinthe/index.xml" rel="self" type="application/rss+xml"/><item><title>GraphQL with Absinthe on Phoenix - Authentication</title><link>http://www.wbotelhos.com/graphql-with-absinthe-on-phoenix-authentication/</link><pubDate>Tue, 24 Aug 2021 00:00:00 -0300</pubDate><guid>http://www.wbotelhos.com/graphql-with-absinthe-on-phoenix-authentication/</guid><description>Updated at: Jul 24, 2023 In the last article about Mutation, we learned how to create records in an easy way, so now we have searches and insertions but we still do not control how the user access that API. For security reasons or just for control of access we need to implement the API Authentication where only logged users can access it.
Goal Authenticate the user and restrict the API to only the logged ones.</description></item><item><title>GraphQL with Absinthe on Phoenix - Mutation</title><link>http://www.wbotelhos.com/graphql-with-absinthe-on-phoenix-mutation/</link><pubDate>Sun, 08 Aug 2021 00:00:00 -0300</pubDate><guid>http://www.wbotelhos.com/graphql-with-absinthe-on-phoenix-mutation/</guid><description>Updated at: Jul 23, 2023 In the last article about GraphQL, we learned how to create a Query and how to avoid N + 1. The systems need to fetch data but the most of time we need to create these data too and GraphQL has a mechanism called Mutation to do this job.
Goal Create a Mutation to save a book using the code of the last article
Mutation The Mutation works very similar to Query, it queries the data in the same way, but after creating the record, and as expected we receive the input data as a parameter, like in Query, but instead it be used as a filter it&amp;rsquo;s used as a parameter to be inserted into the database.</description></item><item><title>GraphQL with Absinthe on Phoenix - Query and Dataloader</title><link>http://www.wbotelhos.com/graphql-with-absinthe-on-phoenix-query-and-dataloader/</link><pubDate>Tue, 03 Aug 2021 00:00:00 -0300</pubDate><guid>http://www.wbotelhos.com/graphql-with-absinthe-on-phoenix-query-and-dataloader/</guid><description>Updated at: Jul 23, 2023 One thing is true, GraphQL is here to stay. This query language is very useful since you can just declare the fields you can have, but choose what you want in each request. It&amp;rsquo;ll avoid you to create combinations of logic that return fields for different purposes.
Goal We&amp;rsquo;ll learn how to use GraphQL on Phoenix with the help of Absinthe and how to deal with Queries and how to avoid N + 1 with the help of Dataloader.</description></item></channel></rss>