Bug Reports

If you were linked to this page from the README or Issues, don't worry! I would love to hear your feedback, but you may have left some helpful or important information out of your bug report.

1. Before submitting your report

• Confirm you are using the latest version of LookupBy. Try bundle update lookup_by. Your issue may already be fixed.
• Search the existing Issues to see if a similar bug has already been reported.
• If you find a security bug, please do not use the issue tracker. Email me at thecompanygardener@gmail.com.

2. When submitting a report

• Include the LookupBy version.
• Include the Ruby and Rails versions: ruby -v, rails --version.
• Include the gem name and version that provides your database adapter.
• Include the PostgreSQL version.
• Include the error class, message, and backtrace if you are getting an error.

3. Many bugs require additional information

• Attempt to create an rspec test that reproduces the bug. See spec/* and spec/dummy.
• Attempt to isolate the bug in a small application and provide a link to its source.

Please keep in mind, this is an open-source project made possible by the contributions of volunteers. Be polite and provide as much information as possible to make it easier to diagnose and fix your bug.

4. The issue tracker is available here:

https://github.com/companygardener/lookup_by/issues