Skip to content

3. Issue Guidelines and Bug Reports

andrewikenberry edited this page May 22, 2020 · 1 revision

bugs

Before opening a new issue:

  • check to see if there is an existing issue that covers what you're experiencing.
  • check to see if there is an open Pull Request that addresses the potential issue.

Once you've determined there's no existing issue for what you're experiencing:

  • describe the issue based on the behavior you were expecting
  • post complete error messages using markdown code fencing.
  • provide a description with complete steps for replicating the issue.
  • demonstration code should be complete, correct and the minimum amount necessary to reproduce the issue

features

Additional modules, features, etc. can be requested via github issues as well. There are labels specifically for these things.

When creating a new request, please be as descriptive as possible.