10.0.15 • Published 2 years ago

transversal v10.0.15

Weekly downloads
-
License
ISC
Repository
github
Last release
2 years ago

Transversal

Transversal is an open-source package that aids developers in utilizing GraphQL's dynamic querying language to auto-generate schemas, queries, and mutations on the frontend from the query template initially setup in the backend. Transversal leverages Redis' in-memory caching mechanism to quickly reference server-side caching.

License Contributions

Table of Contents

Description

Transversal employs methods for the backend engineer to simply call its library to auto-generate the database schema for use by the front end developer — allowing one half of the usual setup to be abstracted away — and offers a quick Redis caching option if the team so chooses! 🚀

Features

  • GraphQL automation stemming from the backend
  • Rapid frontend development
  • Redis caching optional
  • WebSocket for fast frontend notice from the backend

Installation

To start using this dev tool, developers establish their existing mongoDB URI link and start simply by creating a query template on the backend. Let’s get started! Run ‘npm install transversal’ and ‘npm install transversal-client’ and let’s roll on to the backend!

npm install transversal

npm install transversal-client

Getting Started

Back-end

Extra Feature — As mentioned above, we’ve put some added tooling into this dev tool to make development faster, and this is a good time to mention the first — WebSocket for immediate up-to-date changes on the frontend if the backend changes.

This WebSocket option is available by establishing an event listener. While this WebSocket is established any changes to the backend template for auto-generation is immediately updated for our frontend team members. We encourage the use of a WebSocket, as our focus is quick production and iteration, but it’s not required.

const server = http.createServer(app);

const json = transversal.jsonStringify(transversal);

const socket = transversal.instantiateSocket(server, 'http://localhost:8080');

socket.openConnection(json);

Now we dive into the real productivity improvement. Simply start by creating a Transversal class (OOP approach) by calling the transversal() method that takes three arguments — the team’s GraphQL schema, Redis Client, and an origin.

const transversal = new Transversal(schema, redisClient, origin);

After we’ve instantiated the class, we can focus on bringing in our queries and mutations. Let’s get auto-generating and establish GraphQL’s types from the connected database, which we’ll call generateFieldSchema().

transversal.generateFieldSchema();

When setting up GraphQL queries or mutations, you can use Transversal’s generateQuery() and generateMutation() method. But first, we need to define the arguments for the resolver if any, and the resolver itself. Then we need to pass in the query/mutation name in which we want to register, and the field schema to reference the arguments for the resolver if any, if none then null, and the resolver.

Queries

const userArgs = {  
    age: { type: GraphQLInt },  
    height: { type: GraphQLInt },  
};

const userResolver = async (parent, args) => {  
    const users = await User.find({   
       age: args.age,   
       height: args.height   
    });  
    return users;  
};

transversal.generateQuery(queryName, fieldSchemaName, resolver, args);

Mutations

const addUserArgs = {  
    firstName: { type: GraphQLString },  
    lastName: { type: GraphQLString },  
    age: { type: GraphQLInt },  
    height: { type: GraphQLInt },  
};

const addUserResolver = async (parent, args) => {  
    const users = await User.create({  
        firstName: args.firstName,  
        lastName: args.lastName,  
        age: args.age,  
        height: args.height,  
    });  
    return users;  
};

transversal.generateMutation(queryName, fieldSchemaName, resolver, args);

It wouldn’t be such a great tool if it didn’t allow for the flexibility that GraphQL sets out to establish in its paradigm. The tool allows you to create your own custom field schema types on the fly by calling generateCustomFieldSchema() method by passing in the custom schema and the schema name you want to register.

const customSchema = {  
    firstName: 'String',  
    lastName: 'String',  
    age: 'Number',  
    height: 'Number',  
    school: {  
        name: 'String',  
        year: 'Number',  
        code: {  
            code: 'String',  
        },  
    },  
    messages: [{ message: 'String' }],  
};

transversal.generateCustomFieldSchema(customSchema, 'customQuery');

Final Feature — For our final integrated feature, caching. Modern applications, especially those with growing number of users and requests, should implement caching to help server data faster. That’s why we’ve decided to create an out-of-the-box Redis caching attachment available on request at your discretion.

Redis

The open source, in-memory data store used by millions of developers as a database, cache, streaming engine, and… read more redis.io

Local

const redisClient = redis.createClient({  
    host: '127.0.0.1',  
    port: <port>  
});

Microservice

const redisClient = redis.createClient({  
    url: process.env.REDIS_URI  
});

When initially creating the Transversal class, one of the arguments calls for a Redis client URI. If you prefer to use caching with your transversal package, it’s simple to get started. There are two general options, create a local Redis service running side by side with your back-end server (monolithic), or run Redis as a micro service. By flagging this feature on a client-side query, caching will be initiated for that request drastically increasing the latency. See the Redis documentation, you won’t be disappointed.

Front-end

Now for the payoff! On the frontend, import the TransversalClient and instantiate it with your preferred endpoint to set up the WebSocket connection.

import { TransversalClient } from 'transversal-client';

const transversal = new TransversalClient.default('http://localhost:3000');

Make a call to getTransversalInstance() method to get the gql object containing all the queries and mutations templates needed to make API calls and store it in state where it can easily be accessed.

transversal.getTransversalInstance().then((data) => {  
    console.log('gql data from server', data.gql);  
    setGql(data.gql);  
});

Making queries and mutations are done simply by calling transversalQuery() method and passing arguments. You would first need to specify the name of the query or mutation, arguments required (as we saw on the backend previously), specify if you want the call to come from the cache or server, and the last argument can be omitted if you want everything to be returned from the api call. If not, just pass in a custom shape(string) for your data to fill.

transversal.transversalQuery(  
    gql.getUsers,  
    {  
      age: 10,  
      height: 10,  
    },  
    false  
);

And that’s it! You’ve streamlined auto-generated schemas for GraphQL. 🚀

Further Documentation

https://transversal.dev

Contributions

Consider contributing, craft it to your needs and let us know your experience. Open issues, reach out to the team, we want to hear from you! Let us know!

Development Team

License

This product is licensed under the MIT License - see the LICENSE.md file for details.

Product developed under tech accelerator OS Labs.

10.0.5

2 years ago

10.0.6

2 years ago

10.0.7

2 years ago

1.0.39

2 years ago

10.0.8

2 years ago

1.0.38

2 years ago

10.0.9

2 years ago

10.0.0

2 years ago

10.0.1

2 years ago

10.0.2

2 years ago

10.0.3

2 years ago

1.0.40

2 years ago

1.0.44

2 years ago

1.0.42

2 years ago

1.0.41

2 years ago

1.0.0-test

2 years ago

10.0.13

2 years ago

10.0.12

2 years ago

10.0.11

2 years ago

10.0.10

2 years ago

10.0.15

2 years ago

10.0.14

2 years ago

1.0.28

2 years ago

1.0.27

2 years ago

1.0.33

2 years ago

1.0.32

2 years ago

1.0.21

2 years ago

1.0.31

2 years ago

1.0.30

2 years ago

1.0.37

2 years ago

1.0.26

2 years ago

1.0.36

2 years ago

1.0.25

2 years ago

1.0.35

2 years ago

1.0.24

2 years ago

1.0.34

2 years ago

1.0.2

2 years ago

1.0.1

2 years ago

1.0.0

2 years ago