Skip to main content

NestJS API Integration With GraphQL Using Code First Approach


What Is GraphQL?:

GraphQL is a query language for your API and a server-side runtime for executing queries by using a schema type system you defined for your data. GraphQL is not tied to any specific programming language(like NestJS, Java, .NET, etc) or database or storage engine.

How GraphQL Different From Rest API:

  • GraphQL exposes a single endpoint.
  • Http-Post is the only Http verb recommended by supported by GraphQL API.
  • Client applications(consumers of GraphQL API) can give instructions to GraphQL API about the response data.

Code First vs Schema Approach:

Code First Approach:

In Code First Approach we use Typescript class to which need to apply GraphQL decorator on top of classes and also on top of properties inside of the class. These decorators help to auto-generate the raw GraphQL Schema. So in Code First Approach we no need to learn or concentrate to write the GraphQL Schema.

Schema First Approach:

GraphQL SDL(schema definition language) is a new syntactic query type language, in this approach which we need to learn new kinds of syntax. Click here to explore NestJS GraphQL Schema First Approach.

Create NestJS Application:

We will walk through with a simple NestJS Application to integrate GraphQL API in Code First Approach.
NestJS CLI Installation Command:
npm i -g @nestjs/cli
NestJS Application Creation Command:
nest new your-project-name

Install GraphQL Packages:

Let's install the following GraphQL supporting packages for the NestJS application.
1. npm i --save @nestjs/graphql
2. npm i --save graphql-tools
3. npm i --save graphql
4. npm i apollo-server-express

Define Object Type:

In Code First Approach we define Object Types which will generate the GraphQL Schema automatically. Each Object Type we define should represent the application domain object(means table of our database).

Let's define an Object Type class in our application as below.
src/cow.breeds/cow.breeds.ts:
import { ObjectType, Field, Int } from '@nestjs/graphql';

@ObjectType()
export class CowBreed {
  @Field(type => Int)
  id: number;
  @Field()
  name: string;
  @Field(type => Int, { nullable: true })
  maxYield?: number;
  @Field(type => Int, { nullable: true })
  minYield?: number;
  @Field({ nullable: true })
  state?: string;
  @Field({ nullable: true })
  country?: string;
  @Field({ nullable: true })
  Description?: string;
}
  • By decorating class with '@ObjectType()' decorator makes class as GraphQL Object Type. Every property to be registered with '@Fied()' decorator. 
  • This '@Field()' decorator comes with different overloaded options which help to explicitly define property type and whether the property is nullable or not. 
  • TypeScript types like 'string' and 'boolean' are similar to GraphQL types, so for those types we no need to explicitly defined the type of the property in '@Field()' decorator, but other TypeScript types like number, complex type are not understand by the GraphQL '@Field()' decorator, in that case, we need to explicitly pass the type using arrow function like '@Field(type => Int)'. 
  • Similarly explicitly defining property is nullable by inputting as an option to decorator like '@Field({nullable:true})'.
  • GraphQL Schema will be generated based on this ObjectType class automatically which we explore in upcoming steps.

Service Provider:

In general service provider contains logic to communicate with the database and fetches the data to serve. In this sample, we are not going to implement any database communication, but we will maintain some static data in the service provider class as below.
src/cow.breeds/cow.breed.service.ts:
import { CowBreed } from './cow.breed';
export class CowBreedService {
    cowBreeds: CowBreed[]=[{
        id : 1,
        name: "Gir",
        maxYield:6000,
        minYield:2000,
        country: "India",
        state: "Gujarat",
        Description:"This breed produces the highest yield of milk amongst all breeds in India. Has been used extensively to make hybrid 	     v         varieties, in India and in other countries like Brazil"
    }];
	// while testing add more items in the list

    getAllCows(){
        return this.cowBreeds;
    }

    getCowById(id:number){
        return this.cowBreeds.filter(_ => _.id == id)[0];
    }
}
Now register this newly created service provider in the app.module.ts file.
import { CowBreedService } from './cow.breeds/cow.breed.service';

@Module({
  providers: [CowBreedService],
})
export class AppModule {}

Resolver:

Resolver is used to implement GraphQL operations like fetching and saving data, based default GraphQL Object Types like  'Query' Object Type(contains methods for filtering and fetching data), 'Mutation' Object Type(contains methods for creating or updating data).

Let's create a resolver class with Query Object Type as below.
src/cow.breeds/cow.breed.resolver.ts: 
import {Resolver, Query, Args, Int} from '@nestjs/graphql';
import { CowBreedService } from './cow.breed.service';
import {CowBreed} from './cow.breed';

@Resolver()
export class CowBreedResolver {
  constructor(private cowBreedService: CowBreedService) {}

  @Query(returns => [CowBreed])
  async getAllCows(){
    return await this.cowBreedService.getAllCows();
  }

  @Query(returns => CowBreed)
  async getCowById(@Args('id',{type:() => Int}) id:number){
    return await this.cowBreedService.getCowById(id);
  }
}
To make typescript class resolver need to decorate the class with '@Resolver'. '@Query()' decorates defines the method as Query Object Type methods. Here we decorated '@Query()' to the methods which return the data. In Code First Approach inside '@Query()' decorator needs to pass the return type of the data([CowBreed] represents GraphQL array type return the array of CowBreed). Inside the resolver, methods input parameters decorated with '@Args' type to capture the client passed values.

Now register resolver entity in providers array in app.module.ts file.
app.module.ts:
import {CowBreedResolver} from './cow.breeds/cow.breed.resolver';

@Module({
  providers: [CowBreedResolver],
})
export class AppModule {}

Import GraphQLModule:

Let's import GraphQLModule into the app.module.ts.
app.module.ts:
import { GraphQLModule } from '@nestjs/graphql';
import {join} from 'path';

@Module({
  imports: [
    GraphQLModule.forRoot({
      autoSchemaFile:(join(process.cwd(),'src/schema.gql'))
    })
  ],
})
export class AppModule {}
Inside GrphQLModule pass the schema file path('src/schema.gql') where all our application auto-generated schema will be stored. So we need to create a schema file 'schema.gql' as below.
Let's run the NestJS application
NestJS Development Run Command:
npm run start:dev
Now very the way GraphQL Schema Generated automatically as below

GraphQL UI PlayGround:

GraphQL UI Playground is the page which helps as a tool to query our GraphQL API. This Playground gives Schema information, GraphQL Documentation, Intelligence to type the queries more quickly. GraphQL constructed only one endpoint and supports only Http Post verb, so to access this UI Playground simply use the same endpoint in the browser directly.

Fields:

GraphQL is about asking for specific fields on objects on the server. Only requested fields will be served by the server.
Let's query a few fields as follows.
query{
  getAllCows{
    name
    state
    country
  }
}
  • 'query' keyword to identify the request is for fetching or querying data based on 'Query Object Type' at the server. 
  • 'getAllCows' keyword to identify the definition or method inside of the 'Query Object Type'. 
  • 'name', 'state', 'country' are fields inside of the 'CowBreed' GraphQL object type we created. 

Input Argument To Filter Data:

In GraphQL we can pass arguments to filter the Data. Let's construct the query as below with a filtering argument.
query{
  getCowById(id:2){
    id,
    name,
    state,
    country,
    Description
  }
}

Aliases:

While querying the GraphQL API with schema definition names like 'getAllCows', 'getCowById' are more self-explanatory, which good for requesting the API. But API on returning a response uses the same definition name as main object name which looks bit different naming convention for JSON response object. In GraphQL to overcome this scenario, we can use 'Aliases' names which are defined by the client, the API will serve the response with those names.
query{
   Cows:getAllCows{
    name
    state,
    country,
    Description
   }
}

Fragments:

Fragments in GraphQL API mean comparison between two or more records. A comparison between 2 or more items is very easy in GraphQL.
query{
   Cows1:getCowById(id:1){
    name
    state,
    country,
    Description
   }
  Cows2:getCowById(id:1){
    name
    state,
    country,
    Description
   }
  Cows3:getCowById(id:1){
    name
    
   }
}
Defining a schema definition payload multiple times inside of the query object is called Fragments. The fragment is only possible between the same type of schema definition if you try to execute between different schemas that lead to error. In each definition you can define any number of field names, it is not mandatory to define the same number field names in all definitions as in the above query.

Mutation:

GraphQL Mutation object type deals with data updates. All the definitions in the Mutation object type have the responsibility of saving or updating the data to storage (like a database).

For saving data in the Mutation object type definition we need to pass an argument that should be an object. In GraphQL to create an argument object, we need to construct an object type as follows.
src/cow.breeds/cow.breed.input.ts:
import { Int, Field, InputType } from '@nestjs/graphql';
@InputType()
export class CowBreedInput {
  @Field(type => Int)
  id: number;
  @Field()
  name: string;
  @Field(type => Int, { nullable: true })
  maxYield?: number;
  @Field(type => Int, { nullable: true })
  minYield?: number;
  @Field({ nullable: true })
  state?: string;
  @Field({ nullable: true })
  country?: string;
  @Field({ nullable: true })
  Description?: string;
}
In NestJS GraphQL using '@Args()' decorator can capture the input values from the client, but in 'Mutation Object Type' queries involved in the creation or update of data which involves in more number of properties. So to capture the complex object of data using '@Args()'  we need to create a class and it should be decorated with '@InputType'.
Hint:
'ObjectType()' decorator are only used to represent the domain object of the application(database tables). 'ObjectType()' can not used to capture the data from client. So to capture the data from the client we need to use 'InputType()' Object Types.
Let's update service provider logic to save a new item as below.
src/cow.breeds/cow.breed.service.ts:
export class CowBreedService {
    // hidden code for display purpose
    addCow(newItem:any):CowBreed{
        this.cowBreeds.push(newItem);
        return newItem;
    }
}
Now define a 'Mutation Object Type' query in resolver class as follows.
src/cow.breeds/cow.breed.resolver.ts:
import {CowBreedInput} from './cow.breed.Input';

@Resolver()
export class CowBreedResolver {
  // hidden code for display purpose
  @Mutation(returns => CowBreed)
  async addCow(@Args('newCow') newCow:CowBreedInput){
    var cow = await this.cowBreedService.addCow(newCow);
    return cow;
  }
}
Let's run the application and check autogenerated GraphQL Schema for Mutation Object Type.
Now to post the data from the client to GraphQL API, the client uses a syntax called GraphQL variables, these variables take JSON Object as input data. 
mutation($newCow:CowBreedInput!){
  addCow(newCow:$newCow){
    id,
    name,
    maxYield,
    minYield,
    state,
    country,
    Description
  }
}


{
  "newCow": {
    "id": 4,
    "name": "Hallikar",
    "maxYield": null,
    "minYield": null,
    "state": "Karnataka",
    "country": "India",
    "Description": "Draught breed both used for road and field agricultural operations. Closely related to Amrit Mahal. However, are much thinner and produce low yields of milk."
  }
}

Wrapping Up:

Hopefully, this article will help to understand the GraphQL API integration in the NestJS application using Code First Approach. I love to have your feedback, suggestions, and better techniques in the comment section.

Refer:

Follow Me:

Labels:

Comments

Post a Comment

Popular posts from this blog

Angular 14 Reactive Forms Example

In this article, we will explore the Angular(14) reactive forms with an example. Reactive Forms: Angular reactive forms support model-driven techniques to handle the form's input values. The reactive forms state is immutable, any form filed change creates a new state for the form. Reactive forms are built around observable streams, where form inputs and values are provided as streams of input values, which can be accessed synchronously. Some key notations that involve in reactive forms are like: FormControl - each input element in the form is 'FormControl'. The 'FormControl' tracks the value and validation status of form fields. FormGroup - Track the value and validate the state of the group of 'FormControl'. FormBuilder - Angular service which can be used to create the 'FormGroup' or FormControl instance quickly. Form Array - That can hold infinite form control, this helps to create dynamic forms. Create An Angular(14) Application: Let'
3 comments
Read more

.NET 7 Web API CRUD Using Entity Framework Core

In this article, we are going to implement a sample .NET 7 Web API CRUD using the Entity Framework Core. Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, and desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains programming functions that can be requested via HTTP calls either to fetch or update data for their respective clients. Some of the Key Characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build the REST full services. Install The SQL Server And SQL Management Studio: Let's install the SQL server on our l
3 comments
Read more

ReactJS(v18) JWT Authentication Using HTTP Only Cookie

In this article, we will implement the ReactJS application authentication using the HTTP-only cookie. HTTP Only Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing the JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-ONly cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use the authentication with HTTP-only JWT cookie then we no need to implement the custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To authenticate our client application with JWT HTTP-only cookie, I developed a NetJS(which is a node) Mock API. Check the GitHub link and read the document on G
3 comments
Read more

.NET6 Web API CRUD Operation With Entity Framework Core

In this article, we are going to do a small demo on AspNetCore 6 Web API CRUD operations. What Is Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains a programming function that can be requested via HTTP calls to save or fetch the data for their respective clients. Some of the key characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build REST full services. Create A .NET6 Web API Application: Let's create a .Net6 Web API sample application to accomplish our
6 comments
Read more

Angular 14 State Management CRUD Example With NgRx(14)

In this article, we are going to implement the Angular(14) state management CRUD example with NgRx(14) NgRx Store For State Management: In an angular application to share consistent data between multiple components, we use NgRx state management. Using NgRx state helps to avoid unwanted API calls, easy to maintain consistent data, etc. The main building blocks for the NgRx store are: Actions - NgRx actions represents event to trigger the reducers to save the data into the stores. Reducer - Reducer's pure function, which is used to create a new state on data change. Store - The store is the model or entity that holds the data. Selector - Selector to fetch the slices of data from the store to angular components. Effects - Effects deals with external network calls like API. The effect gets executed based the action performed Ngrx State Management flow: The angular component needs data for binding.  So angular component calls an action that is responsible for invoking the API call.  Aft
8 comments
Read more

Unit Testing Asp.NetCore Web API Using xUnit[.NET6]

In this article, we are going to write test cases to an Asp.NetCore Web API(.NET6) application using the xUnit. xUnit For .NET: The xUnit for .Net is a free, open-source, community-focused unit testing tool for .NET applications. By default .Net also provides a xUnit project template to implement test cases. Unit test cases build upon the 'AAA' formula that means 'Arrange', 'Act' and 'Assert' Arrange - Declaring variables, objects, instantiating mocks, etc. Act - Calling or invoking the method that needs to be tested. Assert - The assert ensures that code behaves as expected means yielding expected output. Create An API And Unit Test Projects: Let's create a .Net6 Web API and xUnit sample applications to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor. Create a fo
7 comments
Read more

Angular 14 Crud Example

In this article, we will implement CRUD operation in the Angular 14 application. Angular: Angular is a framework that can be used to build a single-page application. Angular applications are built with components that make our code simple and clean. Angular components compose of 3 files like TypeScript File(*.ts), Html File(*.html), CSS File(*.cs) Components typescript file and HTML file support 2-way binding which means data flow is bi-directional Component typescript file listens for all HTML events from the HTML file. Create Angular(14) Application: Let's create an Angular(14) application to begin our sample. Make sure to install the Angular CLI tool into our local machine because it provides easy CLI commands to play with the angular application. Command To Install Angular CLI npm install -g @angular/cli Run the below command to create the angular application. Command To Create Angular Application ng new name_of_your_app Note: While creating the app, you will see a noti
6 comments
Read more

Part-1 Angular JWT Authentication Using HTTP Only Cookie[Angular V13]

In this article, we are going to implement a sample angular application authentication using HTTP only cookie that contains a JWT token. HTTP Only JWT Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-Only cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use authentication with HTTP only JWT cookie then we no need to implement custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To implement JWT cookie authentication we need to set up an API. For that, I had created a mock authentication API(Using the NestJS Se
Post a Comment
Read more

ReactJS(v18) Authentication With JWT AccessToken And Refresh Token

In this article, we are going to do ReactJS(v18) application authentication using the JWT Access Token and Refresh Token. JSON Web Token(JWT): JSON Web Token is a digitally signed and secured token for user validation. The JWT is constructed with 3 important parts: Header Payload Signature Create ReactJS Application: Let's create a ReactJS application to accomplish our demo. npx create-react-app name-of-your-app Configure React Bootstrap Library: Let's install the React Bootstrap library npm install react-bootstrap bootstrap Now add the bootstrap CSS reference in 'index.js'. src/index.js: import 'bootstrap/dist/css/bootstrap.min.css' Create A React Component 'Layout': Let's add a React component like 'Layout' in 'components/shared' folders(new folders). src/components/shared/Layout.js: import Navbar from "react-bootstrap/Navbar"; import { Container } from "react-bootstrap"; import Nav from "react-boot
Post a Comment
Read more

A Small Guide On NestJS Queues

NestJS Application Queues helps to deal with application scaling and performance challenges. When To Use Queues?: API request that mostly involves in time taking operations like CPU bound operation, doing them synchronously which will result in thread blocking. So to avoid these issues, it is an appropriate way to make the CPU-bound operation separate background job.  In nestjs one of the best solutions for these kinds of tasks is to implement the Queues. For queueing mechanism in the nestjs application most recommended library is '@nestjs/bull'(Bull is nodejs queue library). The 'Bull' depends on Redis cache for data storage like a job. So in this queueing technique, we will create services like 'Producer' and 'Consumer'. The 'Producer' is used to push our jobs into the Redis stores. The consumer will read those jobs(eg: CPU Bound Operations) and process them. So by using this queues technique user requests processed very fastly because actually
9 comments
Read more