Skip to content

Latest commit

 

History

History
182 lines (123 loc) · 4.14 KB

CONTRIBUTING.md

File metadata and controls

182 lines (123 loc) · 4.14 KB
Raw

Contributor Guide

Thank you for your interest in improving this project. This project is open-source under the MIT license and welcomes contributions in the form of bug reports, feature requests, and pull requests.

Here is a list of important resources for contributors:

How to report a bug

Report bugs on the Issue Tracker.

When filing an issue, make sure to answer these questions:

  • Which operating system and Python version are you using?
  • Which version of this project are you using?
  • What did you do?
  • What did you expect to see?
  • What did you see instead?

The best way to get your bug fixed is to provide a test case, and/or steps to reproduce the issue.

How to request a feature

Request features on the Issue Tracker.

How to set up your development environment

You need Python 3.10+ and the following tools:

Install pipx:

python -m pip install --user pipx
python -m pipx ensurepath

Install Poetry:

pipx install poetry

Install Nox and nox-poetry:

pipx install nox
pipx inject nox nox-poetry

Install the pre-commit hooks

nox --session=pre-commit -- install

Install the package with development requirements:

poetry install

You can now run an interactive Python session, or your app:

poetry run python
poetry run datadoc

Config for local development

We use a python package called python-dotenv for configuration management. This gives two possibilities for sourcing configuration:

  1. Environment variables.
  2. A file called .env by convention.

To set up for local development run this command from the root of the repo.

  1. Create a file src/datadoc/.env

  2. Place the following lines in the file:

    DATADOC_DASH_DEVELOPMENT_MODE=True
DATADOC_LOG_LEVEL=debug

To see all configuration options, see src/datadoc/config.py

How to test the project

Run the full test suite:

nox

List the available Nox sessions:

nox --list-sessions

You can also run a specific Nox session. For example, invoke the unit test suite like this:

nox --session=tests

Unit tests are located in the tests directory, and are written using the pytest testing framework.

Running the Dockerized Application Locally

docker run -p 8050:8050 \
-v $HOME/.config/gcloud/application_default_credentials.json/:/application_default_credentials.json \
-e GOOGLE_APPLICATION_CREDENTIALS="/application_default_credentials.json" \
datadoc

Release process

Run the relevant version command on a branch e.g.

poetry version patch
poetry version minor

Commit with message like Bump version x.x.x -> y.y.y.

Open and merge a PR.

How to submit changes

Open a pull request to submit changes to this project.

Your pull request needs to meet the following guidelines for acceptance:

  • The Nox test suite must pass without errors and warnings.
  • Include unit tests. This project maintains 100% code coverage.
  • If your changes add functionality, update the documentation accordingly.

Feel free to submit early, though—we can always iterate on this.

To run linting and code formatting checks before committing your change, you can install pre-commit as a Git hook by running the following command:

nox --session=pre-commit -- install

It is recommended to open an issue before starting work on anything. This will allow a chance to talk it over with the owners and validate your approach.