Skip to content

Latest commit

 

History

History
179 lines (119 loc) · 5.54 KB

DEVELOPING.md

File metadata and controls

179 lines (119 loc) · 5.54 KB
Raw

Developing

Prerequisites

Node.js

Node.js version 14.16.0 is required at the time of writing. nvm is recommended for managing your Node.js installation, and we provide a .nvmrc file to aid you in installing and using the correct version of Node.js.

Yarn

Once you have Node.js installed, you should globally install Yarn by running the following:

npm install -g yarn

Cloning the code

If you just want to snoop around, clone our repository using:

https://github.com/neo4j/graphql.git

If you want to make a contribution, fork our repository and perform a clone, preferably over SSH:

[email protected]:USERNAME/graphql.git

You will then need to add our repository as an upstream:

git remote add upstream [email protected]:neo4j/graphql.git

You can then fetch and merge from the upstream to keep in sync.

Getting started

After cloning the repository, simply run the following from the root to get up and running:

yarn install

Code editor

Visual Studio Code comes highly recommended for working in this repository, and we additionally recommend the following extensions:

The Jest extension should automatically detect the tests for this repository and watch them in the Status Bar.

Testing

Testing locally

In order to run all of the tests, you will need to have a local instance of Neo4j running! We highly recommend Neo4j Desktop to easily get up and running with a local Neo4j instance.

  1. Create and start a new DBMS with a database named neo4j (default).

  2. Install APOC plugin for that DB.

  3. Create appropriate user by running the following command in the DB:

    CREATE USER admin
SET PASSWORD "password"
SET PASSWORD CHANGE NOT REQUIRED
SET STATUS ACTIVE

  4. Grant roles to admin user:

    GRANT ROLE admin to admin

  5. Run tests with yarn test.

Tests are run using Jest, which has been configured to allow for execution of test suites at any level in the project.

You can execute tests with a different database, user and password with the following command:

NEO_URL=neo4j://localhost:7687 NEO_USER=admin NEO_PASSWORD=password yarn test

The above command can additionally be run from packages/graphql, packages/ogm, or any directory where there is a jest.config.js file!

Additionally, for projects which have the appropriate Yarn scripts setup, you can run individual test suites. For instance, to run the TCK test suite of @neo4j/graphql, run the following from packages/graphql:

yarn test:tck

Testing using docker

npm run test-docker

Linting/formatting

We use ESLint for linting and Prettier for code formatting. Contributions must adhere to our linting and formatting rules.

Adding a new project to the monorepo

For the sake of completeness, add an entry for the new project into the following files in the root of the repository:

  • tsconfig.json (references entry)
  • jest.config.base.js (moduleNameMapper entry)

Dependencies within the monorepo

Adding dependencies within the monorepo is a little bit tricky because of the fact that we need to use uncompiled TypeScript code.

This section will contain a couple of example use cases, one for production dependencies and one for test dependencies. They will use an example project with name "project" in packages/project, and the dependency in question will be @neo4j/graphql.

Production dependencies

First things first, install the dependency as you normally would:

yarn add @neo4j/graphql

Now, inside packages/project/src/tsconfig.json, this will need to look something like:

{
    "extends": "../../../tsconfig.base.json",
    "compilerOptions": {
        "baseUrl": "./",
        "outDir": "../dist",
        "paths": {
            "@neo4j/graphql": ["../../graphql/src"]
        }
    },
    "references": [{ "path": "../../graphql/src/tsconfig.json" }]
}

The real key entries here are:

  • baseUrl - for all of the relative references in this file, this will tell tsc where to start from
  • paths - this will translate import statements in code to the relative dependency
  • references - gives TypeScript "permission" to accesss the projects at these paths

Finally, it is highly likely that Jest will also need access to this internal dependency, so packages/project/jest.config.js will need to look like:

const globalConf = require("../../jest.config.base");

module.exports = {
    ...globalConf,
    displayName: "@neo4j/graphql-project",
    roots: ["<rootDir>/packages/project/src", "<rootDir>/packages/project/tests"],
    coverageDirectory: "<rootDir>/packages/project/coverage/",
    globals: {
        "ts-jest": {
            tsconfig: "<rootDir>/packages/project/src/tsconfig.json",
        },
    },
};

The magic sauce here is globals/ts-jest/tsconfig, which tells Jest which TypeScript configuration to use.

Test dependencies

Let's say you just need an internal dependency for testing purposes. You would install this as a dev dependency:

yarn add --dev @neo4j/graphql

You then need to follow the steps above, but using packages/project/tests/tsconfig.json instead of the production tsconfig.json file.