v5.0.0

• using PNPM instead of Yarn, learn
• using the Jest framework to add some tests to our project.
• using GitHub Actions for running tests.
• upgrade to support Prisma 4.
• using graphql-parse-resolve-info package in PrismaSelect plugin

[breaking changes] we have a lot of breaking changes

• The config file name changed from pal.(js|json) to be pal.config.(js|json) to fix an issue with windows #230
• PrismaDelete plugin totally removed, and we don't need it now Prisma support this option.
• remove some options from the nexus paljs plugin

 // send custom dmmf if you have custom generated client path for generate input types
  dmmf?: DMMF.Document[];
  // take an array of field names to exclude from any input type
  excludeFields?: string[];
  // take a function and the input object as arg and return array of fields you want to generate
  filterInputs?: (input: DMMF.InputType) => DMMF.SchemaArg[];
  // by default when we create update inputs you will set data like {username: {set: "Ahmed"}} by making this option true you will be able to use it like {username: "Ahmed"} without set.
  // but you will also lose these options for number fields
  // increment: x: Adds x to the current value
  // decrement: x: Subtracts x from the current value
  // multiply: x: Multiplies the current value by x
  // divide: x: Divides the current value by x
  // set: x: Sets the value to x (equivalent to data: { age: 18 })
  doNotUseFieldUpdateOperationsInput?: boolean;

We added them to pal.config.js

excludeInputFields?: string[];
filterInputs?: (input: DMMF.InputType) => DMMF.SchemaArg[];

• SDL first update we changed our way to generate inputs from run time to file system, so we don't need to generate inputs every time we run the server.

// src/graphql/typeDefs.ts
- import { sdlInputs } from '@paljs/plugins';
+ import InputTypes from './InputTypes';

- export default mergeTypeDefs([sdlInputs()]);
+ export default mergeTypeDefs([InputTypes]);