Skip to content

Latest commit

 

History

History
31 lines (16 loc) · 1.58 KB

issue_template.md

File metadata and controls

31 lines (16 loc) · 1.58 KB
Raw

Tips for submitting an issue with slick (read before you submit an issue):

Note: Delete these instructions from the description field before you submit the issue.

  1. Do not use github issues for support questions. For those, first study the documentation and if they do not contain an answer, use one of the community forums (see https://scala-slick.org/community/). Support questions posted as issues will be deleted without reply or further explanation.

  2. If you have a feature request, note that slick is a community project. As such, you need to get somebody to implement your idea and make a pull request.

  3. If you have a bug report, use the applicable parts of the following template (modify as needed):

DESCRIPTION:

Give a short, clear description of the issue. Make sure the title also describes the issue as well as possible.

STEPS TO REPRODUCE:

Describe steps on how to reproduce the bug. Include a bare-bones test case (as small as possible) that demonstrates the bug.

EXPECTED RESULT:

Describe what you expected to see and why.

ACTUAL RESULT:

Describe what you saw. If you got compiler errors or exceptions, include them. When including an exception stack traces, make sure to include also the root cause (search for "Caused by:" in the stack trace).

SETUP:

Describe your set-up (database used, profile, configuration, etc)

As with feature requests, note that slick is a community project and the best way to get bugs fixed is to submit a pull request for fixing it, along with a test case that demonstrates the bug existed prior to the PR and does not after the PR.