myplanet / graphql-server Goto Github PK

It would be good to go through the code base and add typescript support for more robust and secure development and engineering experience

A module should be able to define its own context modifications to the main Apollo context. This means that stand alone modules, such as the user auth module, can provide functions to modify the context if required.

Like NextJS, our implementation should not just be a seed, but an opinionated build system. This means it can be included as a package in other projects, and enforces a certain structure to reading modules, permissions, etc.

The folder structure we be enforced by auto-loading of files in their proper places. Individual modules could also be abstracted out into their own packages, such as one for user auth, etc.

Basically, we want this to be more of a package that can be included and continually updated then a starter seed that is forked and modified.

The repo should be broken down into a number of discrete units that are their own packages using lerna.js.

There will at least be a core module, which will house the main build system and module loader.

Each connector should ideally be its own module, which currently would be redis and postgres.

We should also have a package for sample modules, including one that adds a user model with proper context modification.

Switch over from prisma 1 to prisma 2. This will also require the addition of a postgres docker container for local development, and possible remote deployment depending on deployment needs.