Thanks for your interest in Hasura GraphQL Engine CLI.
You can follow your existing Golang workflow to fork, work on a branch and submit PR. If you're new to forking and working on Golang repositories, please follow the instructions below to make sure the import paths are correct:
- Fork the repo on GitHub
mkdir -p $GOPATH/src/github.com/hasura
cd $GOPATH/src/github.com/hasura
git clone https://github.com/<your-username>/graphql-engine
cd graphql-engine
git remote add upstream https://github.com/hasura/graphql-engine
git checkout -b <branch-name>
make deps
- Work on the feature/fix
- If you modify files in
assets/
, runmake assets
- Add tests and ensure all tests are passing (check Tests section below)
- Commit, push and submit PR
We suggest using realize for faster dev
workflow. The .realize.yaml
config is already included in the repo.
- Install realize
go get github.com/oxequa/realize
- Start realize
realize start
realize
watches the directory for changes and rebuilds the cli whenever a new
change happens. The cli is installed to $GOPATH/bin/hasura
, which should
already be in your PATH
. The config is located at .realize/realize.yaml
.
When you're adding a new feature, it is encouraged to add integration tests (unit tests also if possible) for the functions/api. You should run all the tests and make sure everything passes before submitting the PR.
The tests expect a GraphQL Engine server instance to be running. You can point the tests to any GraphQL Engine server but please note that the database should be empty. The easiest way to do this is to run Postgres and GraphQL Engine using Docker Compose. Once the server is running, you can run the tests by executing the make command:
HASURA_GRAPHQL_TEST_ENDPOINT=http://localhost:8080 VERSION=dev make test
To build a binary, execute the following command:
# make deps to install all go packages
make build
This will output cross-platform binaries to _output
directory.