Once you head down the GraphQL's path forever will it dominate your destiny.

GraphQL Editor Cli

Translate GraphQL to Anything and make it your one and only source of truth. Schema. Compatible with GraphQL Editor projects( Free and Paid Tiers). So the main goal is to provide interactive experience creating GraphQL as a service.

• GraphQL Editor Cli
  • Installation
    • Global
    • Inside Repo
  • Usage
  • Commmon Options
  • Commands
    • Schema
      • Additional options
    • Typings
      • Additional options
    • Backend
      • Bootstrap
      • Development
      • Models
        • MongoDB
      • Resolvers
      • Deploy to GraphQL Editor Shared Worker
        • Environment inside shared worker
      • Push to cloud
      • Pull from cloud
  • Roadmap

Installation

Global

npm i -g graphql-editor-cli

Inside Repo

npm i -D graphql-editor-cli

then use with npx for example or as a package.json script.

Usage

All comands work in 3 ways.

• You can provide all arguments with flags
• you can get them from local config file
• complete them in interactive modes

In this order CLI will try to get argument.

Commmon Options

All commands also take these options which refer to your GraphQL Editor project

Commands

Schema

Fetch schema from GraphQL Editor project. Schema will be compiled with GraphQL libraries you are using for this project

$ gecli schema

Additional options

Typings

Generate TypeScript typings from GraphQL Editor project.

$ gecli typings

Additional options

Backend

Bootstrap

$ gecli bootstrap

Bootstrap a backend stucco project. It will create folder with package.json stucco.json and eslint and prettier configuration. It is an interactive command. It will create a folder with project name you will provide

Development

$ gecli dev

To start stucco development server reacting to your code changes,

Models

$ gecli models

Generate TypeScript Models from GraphQL types. They are very useful to use with popular Databases

type Person {
  firstName: String!
  lastName: String!
  email: String
  phone: String
  friends: [Person!]!
}

will be transformed to a model file

import type { ModelTypes } from '@/zeus';
export type Person = ModelTypes['Person'];

later on you may want to transform it so it is a database model.

import type { ModelTypes } from '@/zeus';
export type Person = Omit<ModelTypes['Person'], 'friends'> & { friends: string[] };

So you see the concept.

MongoDB

Here is an example how you can use your model in MongoDB.

db.collection<MyModel>.find({})

Resolvers

CLI tool to generate Stucco resolvers in TypeScript from GraphQL fields.

Given the following schema:

type Person {
  firstName: String!
}
type Query {
  people: [Person]!
}
schema {
  query: Query
}

After chosing:

1. Query
2. people

It should generate TypeScript resolver placed in $src/Query/people.ts

import { FieldResolveInput, FieldResolveOutput } from 'stucco-js';
import { PersonCollection } from '../db/collections';
import { DB } from '../db/mongo';
import { Utils } from '../Utils';
import { Person, ResolverType, ValueTypes } from '../graphql-zeus';

export const handler = async (): Promise<FieldResolveOutput> => {};

and append correct entries to stucco.json file.

{
  "resolvers": {
    "Query.people": {
      "resolve": {
        "name": "lib/Query/people"
      }
    }
  }
}

and after running stucco your resolver should work out of the box. Some resolver types however need little code to make them work the way you want.

Deploy to GraphQL Editor Shared Worker

Shared workers are really powerful. With one command you can deploy stucco based backend to them.

gecli deploy --backendZip=https://github.com/aexol-studio/monospace-backend/archive/refs/heads/main.zip

Environment inside shared worker

To pass environment variables use -e flag for deploys. For example

gecli deploy -e DB_URL=https://exampledb.com -e HOME=$HOME

Push to cloud

Sometimes you will want to push to cloud GraphQL Editor back from repo. So editor users can see/test the changes in Editor browser IDE. To do it

$ gecli push

This will clean cloud folder and push cwd to the editor cloud.

Pull from cloud

When you want to move from cloud folder as your service is getting bigger and put the project inside repository. You can use pull command

$ gecli pull

It will pull the project to the project name folder

Roadmap

• [ ] Prisma models from GraphQL types interactive CLI
• [ ] More use cases with other databases and ORMs
• [ ] Deployment of microservices
• [ ] Add colours
• [x] Push files to editor
• [x] Generation of ejected microservices CI