Skip to content

Latest commit

 

History

History
146 lines (87 loc) · 4.16 KB

CONTRIBUTING.rst

File metadata and controls

146 lines (87 loc) · 4.16 KB
Raw

Contributing to EAGERx

If you are interested in contributing to EAGERx, your contributions will fall into three categories:

  1. You want to propose a new Feature and implement it

    • Create an issue about your intended feature, and we shall discuss the design and

    implementation. Once we agree that the plan looks good, go ahead and implement it.

  2. You want to implement a feature or bug-fix for an outstanding issue

    • Look at the outstanding issues here: https://github.com/eager-dev/eagerx/issues
    • Pick an issue or feature and comment on the task that you want to work on this feature.
    • If you need more context on a particular issue, please ask and we shall provide.

  3. You want to create a new EAGERx package

Once you finish implementing a feature or bug-fix, please send a Pull Request

If you are not familiar with creating a Pull Request, here are some guides:

Developing EAGERx

To develop EAGERx on your machine, here are some tips:

  1. Clone a copy of EAGERx from source:
git clone https://github.com/eager-dev/eagerx.git
cd eagerx/
  1. Install Poetry if you haven't done so yet:
curl -sSL https://raw.githubusercontent.com/python-poetry/poetry/master/get-poetry.py | python -
  1. Install EAGERx:
poetry install

Codestyle

We are using black codestyle (max line length of 127 characters).

Please run make codestyle to reformat your code. You can check the codestyle using make check-codestyle and make lint.

Please document each function/method and type them using the following template:

def my_function(arg1: type1, arg2: type2) -> returntype:
    """
    Short description of the function.

    :param arg1: describe what is arg1
    :param arg2: describe what is arg2
    :return: describe what is returned
    """
    ...
    return my_variable

Pull Request (PR)

Before proposing a PR, please open an issue, where the feature will be discussed. This will prevent the proposal of duplicate PRs and also ease the code review process.

Each PR needs to be reviewed and accepted by at least one of the code owners (@bheijden, @jelledouwe). A PR must pass the Continuous Integration tests to be merged with the master branch.

Tests

All new features must add tests in the tests/ folder ensuring that everything works fine. We use pytest. Also, when a bug fix is proposed, tests should be added to avoid regression.

To run tests with pytest:

make pytest

Codestyle check with black and flake8:

make check-codestyle
make lint

Build the documentation:

make doc

Check documentation spelling (you need to install sphinxcontrib.spelling package for that):

make spelling

Semantic Pull Request and Documentation

Please make sure that you use semantic commit messages and add documentation if needed. For example, when committing a fix, your commit message should start with `fix: `, for features with `feat: ` and for breaking changes `BREAKING CHANGE: `. You should add your username in the commit message for each fix, feature or breaking change. The docs can be built as follows.

Make sure EAGERx is installed:

cd [eagerx_root]
poetry install

Activate the Poetry environment:

poetry shell

Build the docs:

make doc

Credits: this contributing guide is based on the one from Stable Baselines3 which in turn is based on the one from PyTorch.