sahilrajput03

Hasura

• Hasura was founded in July, 2017.
• its unicorn: click here

• What is Hasura?

  source: click here

  20 JANUARY, 2020

  3 MIN READ: The Hasura GraphQL Engine is a blazing-fast GraphQL server that gives you instant, realtime GraphQL APIs over Postgres, with webhook triggers on database events, and remote schemas for business logic. Hasura helps you build GraphQL apps backed by Postgres or incrementally move to GraphQL for existing applications using Postgres. The Hasura GraphQL Engine is open-source. You can check out the complete repo here.

• About Hasura Company and Team: click here

• Tanmai Gopal (co-founder)

  Linkedin

  Blogs

• Rajoshi Ghosh(co-founder)

  Linkedin

• watch what is hasura from Tanmai Gopal - click here
• Who is using Hasura? case studies - click here, other companies
• Getting started with hasura locally - Docs: click here
• Getting started with hasura locally - Docs: click here
• Start Locally with docker: Click here
• Fireshipio - Hasura: Click here
• Hasura - Getting Started (Your First Query) @youtube: Click here

// SAMPLE GRAPHQL QUERY VIA FETCH, made by code exporter in Hasura. ~Sahil
/*
This is an example snippet - you should consider tailoring it
to your service.
*/

async function fetchGraphQL(operationsDoc, operationName, variables) {
  const result = await fetch(
    "undefined",
    {
      method: "POST",
      body: JSON.stringify({
        query: operationsDoc,
        variables: variables,
        operationName: operationName
      })
    }
  );

  return await result.json();
}

const operationsDoc = `
  mutation MyMutation($likes: Int = 2) {
    insert_blogs(objects: {title: "awsm blog", year: 2022, url: "google.com", likes: $likes}) {
      affected_rows
      returning {
        author
        id
        likes
        title
        updated_at
        url
        year
        user_id
        created_at
      }
    }
  }
`;

function executeMyMutation(likes) {
  return fetchGraphQL(
    operationsDoc,
    "MyMutation",
    {"likes": likes}
  );
}

async function startExecuteMyMutation(likes) {
  const { errors, data } = await executeMyMutation(likes);

  if (errors) {
    // handle those errors like a pro
    console.error(errors);
  }

  // do something great with this precious data
  console.log(data);
}

startExecuteMyMutation(likes);

Creating managed permissions - Yo

Awesome: Source: Hasura Authorization #EasyGraphQLwHasura, all this in blogpost: Click here.

1. 
2. 
3. Add Table:
4. Add foreign key like that:
5. Add this relationship:
6. We are going to use deafult employees text there:
7. Add the object relationship as well (This is Manager Relation):
8. Add another table and save the table:
9. Now Add foreign key like that:
10. We can (but we don’t) add relation like we added earlier as shwon in there but we’ll use Track way to add relationship this time(see next screenshot):
11. Click on Track All to track all realtions automatically:
12. We can see that relationship is set successfully between payroll and employee:
13. Lest make manager_id field as nullable:
14. Lets add employees now:

We can see that Janet and Michael are added:

Now we use Michael's id as highlighed in above screenshot to be as manager_id for filed of Elanor and Chiddi:

We can see the results as expected:

1. Lets create payroll entries:

Janet (using Janet’s id):

Michael (using Michael’s id):

Elanor (using Elanor’s id):

Chiddi (using Chidd’s id):

Now in payroll we can see all the entries:

1. Querying in graphiql we can see such data which says Michael is manager for Elanor and Chidi:

2. We can see employees for employees i.e., for Michael we can see he has employees as Elanor and Chidi:

3. We can see emoyees and salaries in payroll table:

4. Setting up permission for HR (insert* permission) and save that:

5. Now we clone the permission for select, update and delete as well by doing that:

6. We can see that HR now has all the permissions for insert, select, update and delete:

7. Now we set select permission for employees:

8. Now we set select permission for the employee who is actually a Manager:

9. Make same permission for update as well:

10. We change the name of payroll table to payrolls:

11. Lets make everyone to be able to select everything:

12. Lets clone select permission of Employees(i.e., same above permision) for HR and Managers as well (FYI: Do overwrite the permissions if asked):

Now we can see that everyone can select:

1. Normally we pass roles in the request via jwt token like that..:

BUT for now we are just gonna do it like this for demo (role=HR and id=Jane’s Id):

and we see that HR can select the data.

also, if we put role=Manager and id=Michael’s Id we see that Michael can select data for Elanor and Chidi only:

and Elanor can only select her own data only:

and same for Chidi:

Also we can see that employee can not mutate data bcoz we set that in permission roles that employees can only query data:

And if we use Manager role instead we can see that Manage can mutate and insert data as well:

Changing salary of Elanor by Manager:

Lets see Elanor’s Salary (we can move to payroll table for any employee like that):

and we can see it update correctly (we can use that button to close it though):

Also, if we try to update Janet’s salary by using Manager role we see that its not allowed:

1. Using jwt token for real world scenario. We can use key as anything(using long random key is good though) and also provide type as well for correspoinding alog use to hash the jwt:

Now we can see that we can query using our jwt token(yo!!):