Bug reports

If you think you have found a bug in NEM Library, first make sure that you are testing against the latest version of NEM Library - your issue may already have been fixed. If not, search our issues list on GitHub in case a similar issue has already been opened.

It is very helpful if you can prepare a reproduction of the bug. In other words, provide a small test case which we can run to confirm your bug. It makes it easier to find the problem and to fix it.

Please, take in consideration the next template to report your issue:

Expected Behaviour

Short and expressive sentence explaining what the code should do.

Current Behaviour

A short sentence enplaning what the code does.

Steps to reproduce

For faster issue detection, we would need a step by step description do reproduce the issue.

Provide as much information as you can.

Open a new issue here.

Feature requests

If you find yourself wishing for a feature that doesn't exist in NEM Library, you are probably not alone. There are bound to be others out there with similar needs. Many of the features that NEM Library has today have been added because our users saw the need. Open an issue on our issues list on GitHub which describes the feature you would like to see, why you need it, and how it should work.

Join the development discussion

We love to listen your thoughts about NEM Library, you can find us in Gitter or checkout our About section