March 2020 Summaries

In this tutorial, we will build a movie app using Hasura and gqless. Firstly, we will set up Hasura by creating two tables - movies and characters. We will then create a one-to-many relationship between these two tables. Next, we will set up the React app with necessary dependencies such as gqless, @gqless/react, typescript, and @gqless/cli. After setting up the basic app structure, we will use gqless to fetch data from Hasura without writing any GraphQL queries manually. We will also demonstrate how to list characters for each movie using gqless. Furthermore, we will add React Router for navigation and emotion for styling. To improve performance, we will customize the cache using gqless's extensions by setting keyed values and cached redirects. Finally, we will make some cleanups and add components to list characters for each movie. In conclusion, this tutorial demonstrates how to set up array relationships with Hasura, use gqless with a GraphQL endpoint, and utilize various features of gqless such as automatic data fetching, type generation, and caching behavior extensions.

At Hasura, the team decided to use TypeScript for their Hasura Console due to its compatibility with existing JavaScript code and React components development. They also wanted to enhance developer experience by making things easier and faster. The decision was made after evaluating other options such as PureScript, ReasonML, and Elm. TypeScript's optional static typing allows developers to gradually add type checking where necessary, making it easy for JavaScript developers to transition into using TypeScript.

This article discusses the implementation of authorization systems using Hasura's JSON-based DSL. It provides a brief overview of Hasura's authorization system and explains how to create new roles, set permissions for select, insert, update, and delete operations on tables in the schema. The text then delves into real-world examples such as simple role-based access control, per-resource roles, hierarchical roles, and attribute-based access control. It also touches upon using views to handle more complex scenarios and mentions resources for learning more about authorization rules.

In celebration of five years since its release, some key figures in the GraphQL community have shared their thoughts on how it has changed the way teams communicate and collaborate. They highlighted that GraphQL empowers developers to request for specific data they need, reducing communication overhead with API teams. The most popular feature is GraphiQL, which helps users visualize queries and responses. Some improvements suggested include better support for microservices, more opinionated authorization, easier onboarding for beginners, and handling errors in the query. Challenges of using GraphQL include initial adoption and building a good server that leverages modern trends. The most popular way to convince someone to migrate to GraphQL is by showcasing its features and benefits.

The text discusses best practices for using Hasura, a GraphQL engine. It covers managing business logic through Actions and other approaches such as remote schemas, event triggers, scheduled triggers, and Postgres functions. Fluent GraphQL clients are recommended to prevent GraphQL queries from becoming strings. For dev/staging environments and persisted data, Hasura migrations make management easy. Custom signup flows can be achieved using Actions that call HTTP webhooks or serverless functions. To enable Actions, update the Hasura GraphQL engine to the latest stable version.