Reporting bugs

Bug reports (including wishlist items) can be submitted to RT.

<https://rt.cpan.org/Dist/Display.html?Queue=Type-Tiny>.

Test cases written using Test::More are always appreciated.

Fixing bugs

If something doesn't work as documented, or causes unexpected crashes, and you know how to fix it, then either attach a patch to the bug report (see above) or as a pull request to the project on GitHub.

<https://github.com/tobyink/p5-type-tiny>.

Please try to follow the coding style used in the rest of the project. (Tab indents, spaces for alignment, British English spellings, pod at the end of code but the start of test cases, etc.)

Adding Test Cases

New test cases for the Type::Tiny test suite are always welcome. The coveralls page for Type::Tiny should reveal what parts of the code are most needing good test cases. Any files with below 95% coverage are highest priority.

<https://coveralls.io/github/tobyink/p5-type-tiny>.

Improving Documentation

While the documentation for each package in Type::Tiny is fairly complete, Type::Tiny::Manual needs a bit of work.

Writing Type Libraries

Though I'm unlikely to bundle many more type libraries in this distribution, uploading your own type libraries to CPAN will strengthen the Type::Tiny ecosystem.