Development and contribution guide

Directory Location

If you are working on 0x-mesh, the root directory for the project must be at $GOPATH/src/github.com/0xProject/0x-mesh. 0x Mesh uses Dep for dependency management and does not support Go modules.

Cloning the Repository and Opening PRs

0x Mesh uses two main branches:

1. The development branch contains the latest (possibly unreleased) changes

   and is not guaranteed to be stable.

2. The master branch contains the latest stable release.

If you intend to fork 0x Mesh and open a PR, you should work off of the development branch. Make sure you check out the development branch and pull the latest changes.

git checkout development
git pull

All PRs should use development as the base branch. When opening a new PR, use the dropdown menu in the GitHub UI to select development.

Selecting a branch

Prerequisites

• GNU Make If you are using a Unix-like OS, you probably already have this.

• Go version 1.12.x (or use the version manager called "g"). Go 1.13 is not supported yet (see https://github.com/0xProject/0x-mesh/issues/480).

• Dep package manager

• Node.js version >=11 (or use the nvm version manager)

• Yarn package manager

• golangci-lint version 1.16.0

Installing Dependencies

make deps

Running Tests

Some of the tests depend on having a test Ethereum node running. Before running the tests, make sure you have Docker installed locally and start 0xorg/ganache-cli:

docker pull 0xorg/ganache-cli
docker run -ti -p 8545:8545 -e VERSION=4.3.0 0xorg/ganache-cli

There are various Make targets for running tests:

# Run tests in pure Go
make test-go

# Compile to WebAssembly and run tests in Node.js
make test-wasm-node

# Compile to WebAssembly and run tests in a headless Chrome browser
make test-wasm-browser

# Run tests in all available environments
make test-all

Running the Linters

0x Mesh is configured to use linters for both Go and TypeScript code. To run all available linters, run:

make lint

Managing Dependencies

See https://golang.github.io/dep/docs/daily-dep.html.

Editor Configuration

Visual Studio Code

For VS Code, the following editor configuration is recommended:

{
  // ...

  "editor.formatOnSave": true,
  "go.formatTool": "goimports",
  "go.lintTool": "golangci-lint",
  "go.lintOnSave": "package",
  "go.vetOnSave": "off"

  // ...
}

When working on code with the build tag js,wasm, you might need to add the following to your editor config:

{
    // ...

  "go.toolsEnvVars": {
    "GOARCH": "wasm",
    "GOOS": "js"
  },
  "go.testEnvVars": {
    "GOARCH": "wasm",
    "GOOS": "js"
    }

    // ...
}