<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Graphql on Janik von Rotz</title>
    <link>https://janikvonrotz.ch/tags/graphql/</link>
    <description>Recent content in Graphql on Janik von Rotz</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Jan 2020 14:05:23 +0100</lastBuildDate>
    <atom:link href="https://janikvonrotz.ch/tags/graphql/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Apollo GraphQl server and client sorting</title>
      <link>https://janikvonrotz.ch/2020/01/29/apollo-graphql-server-and-client-sorting/</link>
      <pubDate>Wed, 29 Jan 2020 14:05:23 +0100</pubDate>
      <guid>https://janikvonrotz.ch/2020/01/29/apollo-graphql-server-and-client-sorting/</guid>
      <description>&lt;p&gt;GraphQl is not opinionated about sorting and pagination. It is up to you to implement the sorting for your query. I&amp;rsquo;ve seen various approaches doing that, but none seemed elegant. After compiling a few blog posts and tutorials I came up with the following solution.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Apollo Graphql integration testing in practice</title>
      <link>https://janikvonrotz.ch/2019/12/05/apollo-graphql-integration-testing-in-practice/</link>
      <pubDate>Thu, 05 Dec 2019 10:16:19 +0100</pubDate>
      <guid>https://janikvonrotz.ch/2019/12/05/apollo-graphql-integration-testing-in-practice/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://www.apollographql.com/docs&#34;&gt;Apollo Graphql documention&lt;/a&gt; offers a pretty comprehensive guide on how to &lt;a href=&#34;https://www.apollographql.com/docs/apollo-server/testing/testing&#34;&gt;test your Graphql API&lt;/a&gt;. But sure its different once you implement tests for your non generic project. That is why I wrote this post. First I would like to introduce you to integration tests and how they are different from the other testing levels. And then I&amp;rsquo;ll give you a hands on experience for writing integration tests for Apollo Graphql with &lt;a href=&#34;https://github.com/avajs/ava&#34;&gt;Ava&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Build an Apollo Graphql user authentication for your React app - part 3</title>
      <link>https://janikvonrotz.ch/2019/09/26/build-an-apollo-graphql-user-authentication-for-your-react-app-part-3/</link>
      <pubDate>Thu, 26 Sep 2019 10:31:27 +0200</pubDate>
      <guid>https://janikvonrotz.ch/2019/09/26/build-an-apollo-graphql-user-authentication-for-your-react-app-part-3/</guid>
      <description>&lt;p&gt;This is the final post of my GraphQL Auth series. Before reading this post checkout &lt;a href=&#34;https://janikvonrotz.ch/2019/08/27/build-an-apollo-graphql-user-authentication-for-your-react-app-part-1&#34;&gt;post 1&lt;/a&gt; and &lt;a href=&#34;https://janikvonrotz.ch/2019/08/29/build-an-apollo-graphql-user-authentication-for-your-react-app-part-2&#34;&gt;post 2&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;As mentioned in my last post we need to polish our authentication solution. First we wanna ensure that the JWT token expires. Second, I think the &lt;code&gt;isAuthenticated&lt;/code&gt; directive is insufficient for proper permission management on our types, queries and mutations. We need a role based solution. While the first point is simple to implement, the second is more complex and definitely requires walking through the previous posts.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Build an Apollo Graphql user authentication for your React app - part 2</title>
      <link>https://janikvonrotz.ch/2019/08/29/build-an-apollo-graphql-user-authentication-for-your-react-app-part-2/</link>
      <pubDate>Thu, 29 Aug 2019 19:34:07 +0200</pubDate>
      <guid>https://janikvonrotz.ch/2019/08/29/build-an-apollo-graphql-user-authentication-for-your-react-app-part-2/</guid>
      <description>&lt;p&gt;In my &lt;a href=&#34;https://janikvonrotz.ch/2019/08/27/build-an-apollo-graphql-user-authentication-for-your-react-app-part-1&#34;&gt;last post&lt;/a&gt; we built a Graphql API that handles user authentication and authorization. In particular we added a &lt;code&gt;loginUser&lt;/code&gt; query that returns a JWT token. This token can be used to access restricted resources.&#xA;In this post I will show what the implementation looks like on Reacts side.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Build an Apollo Graphql user authentication for your React app - part 1</title>
      <link>https://janikvonrotz.ch/2019/08/27/build-an-apollo-graphql-user-authentication-for-your-react-app-part-1/</link>
      <pubDate>Tue, 27 Aug 2019 18:35:12 +0200</pubDate>
      <guid>https://janikvonrotz.ch/2019/08/27/build-an-apollo-graphql-user-authentication-for-your-react-app-part-1/</guid>
      <description>&lt;p&gt;I am currently building an &lt;a href=&#34;https://www.apollographql.com/docs/apollo-server/&#34;&gt;Apollo Graphql&lt;/a&gt; API and a &lt;a href=&#34;https://reactjs.org/&#34;&gt;React&lt;/a&gt; web application. The application requires a user authentication functionality in order to enforce access restrictions on the Graphql endpoint. Apollo Graphql does not provide an out-of-the-box-solution and therefore I would like to present my solution.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Raspberry Pi thermometer that connects from anywhere via broadband</title>
      <link>https://janikvonrotz.ch/2018/11/16/raspberry-pi-thermometer-that-connects-anywhere-via-broadband/</link>
      <pubDate>Fri, 16 Nov 2018 20:00:23 +0200</pubDate>
      <guid>https://janikvonrotz.ch/2018/11/16/raspberry-pi-thermometer-that-connects-anywhere-via-broadband/</guid>
      <description>&lt;p&gt;This tutorial is about how to build an online accessible thermometer using the Raspberry Pi 3 B-model.&lt;/p&gt;&#xA;&lt;p&gt;We will start by buying the electronic components and finish with a chart showing the temperature data.&lt;/p&gt;&#xA;&lt;p&gt;Walking through the tutorial requires basic knowledge in working with linux and advanced knowledge in building web applications. Whereas the web application part is optionally.&lt;/p&gt;&#xA;&lt;p&gt;Using a mobile broadband connection and a thermo sensor our Raspberry Pi will measure the temperature and save it to a graphql server.&lt;/p&gt;&#xA;&lt;p&gt;Using react and a graphql client library we will create a chart with the temperature data.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Authenticate Meteor accounts with the Apollo GraphQL API</title>
      <link>https://janikvonrotz.ch/2016/11/12/authenticate-meteor-accounts-with-the-apollo-graphql-api/</link>
      <pubDate>Sat, 12 Nov 2016 10:21:20 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2016/11/12/authenticate-meteor-accounts-with-the-apollo-graphql-api/</guid>
      <description>&lt;p&gt;One of the popular features of Meteor is its accounts package. As you know, it makes it fairly easy to add a user authentication solution to your Meteor app or add support for different oAuth services. With the possibility to integrate an Apollo GraphQL API into your Meteor app this became a bit more difficult. The Apollo stack does not support an out of the box solutions to authenticate users with Meteor accounts. Jonas Helfer, one of the Apollo core devs, proposed &lt;a href=&#34;https://dev-blog.apollodata.com/a-guide-to-authentication-in-graphql-e002a4039d1&#34;&gt;two ways to authenticate users with your app&lt;/a&gt;:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Graphql with Apollo, Meteor and React</title>
      <link>https://janikvonrotz.ch/2016/10/09/graphql-with-apollo-meteor-and-react/</link>
      <pubDate>Sun, 09 Oct 2016 19:39:30 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2016/10/09/graphql-with-apollo-meteor-and-react/</guid>
      <description>&lt;p&gt;For my last project I had to build a web application to administrate a MongoDB database. Due to using Meteor quite a lot I heard about Graphql and the Apollostack. Graphql, which is a specification done by Facebook engineers, promises to be the better REST API (which I hope it is). I became curious and decided the build the server API with Apollo. First I tried to evade using the Meteor as build system as I don&amp;rsquo;t want to get too accustomed to this full-stack ecosystem. However, building a live-reload server and client build system in ES6 with Node.js, Babel and Webpack was simply too much work compared to building this simple web app. So in result this was my stack:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
