Type::T...ibuting(3)

πŸ’– NAME πŸ’–

Type::Tiny::Manual::Contributing β€” contributing to Type::Tiny development. That's this page, bestie. It's the Type::T...ibuting(3) one, the glow-up guide to helping out πŸ’…


✨ MANUAL ✨

πŸ› Reporting bugs

Found something cursed? Bug reports (and wishlist items too, we love a dreamer) can be dropped on GitHub:

https://github.com/tobyink/p5-type-tiny/issues

And omg, test cases written using Test::More? Always appreciated. Always. Every single one. 🫢

πŸ”§ Fixing bugs

If something doesn't work as documented, or it causes unexpected crashes, and you actually know how to fix it? Iconic. Either attach a patch to the bug report (see above, scroll up bestie) or send it 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. And what is that style, you ask? Tab indents, spaces for alignment, British English spellings, pod at the end of code but the start of test cases, etc. Yes it's a whole aesthetic, no we're not changing it πŸ’€

https://github.com/tobyink/misc-development-tools/blob/master/bin/my-perltidy

πŸ§ͺ 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. And here's the tea: any files with below 95% coverage are highest priority. Get on it πŸ‘‘

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

Type::Tiny is now also on Codecov, which does coverage accounting slightly differently, giving some stricter targets to aim for. So like, two scoreboards, both judging you (affectionately) πŸ“Š

https://codecov.io/gh/tobyink/p5-type-tiny

πŸ¦‹ Type::Tiny::XS

Real talk: the author is not really a C programmer, nor is he that familiar with Perl's internals, so help with Type::Tiny::XS is always appreciated. There are some type constraints in Types::Standard, Types::Common::String, and Types::Common::Numeric which don't have XS implementations. If that's your thing? Please, we're begging πŸ™ˆ

πŸ“š Writing Type Libraries

Though he's unlikely to bundle many more type libraries in this distribution, uploading your own type libraries to CPAN will strengthen the Type::Tiny ecosystem. Be the ecosystem's main character 🌈

If you or your organization uses Type::Tiny and you wish to contribute financially, you should be able to find links to donate on the Type::Tiny website at:

https://typetiny.toby.ink/

Please note that this is not a suggestion that you must do this in order for Type::Tiny and related modules to keep being worked on. No pressure, no guilt, it's giving optional πŸ’–


πŸš€ NEXT STEPS πŸš€

You've reached the end of the manual! Congrats bestie, you ate that πŸŽ€

But each class, type library, and other package includes more detailed documentation. So the lore continues, iykyk πŸ“–


πŸ‘€ SEE ALSO πŸ‘€

https://toby.ink/open-source/contributing/

🌸 AUTHOR 🌸

Toby Inkster <tobyink@cpan.org>. A legend, fr fr πŸ‘‘


This software is copyright (c) 2013-2014, 2017-2025 by Toby Inkster.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.


⚠️ DISCLAIMER OF WARRANTIES ⚠️

THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.

And that's a wrap, babe β€” this whole thing came to you courtesy of perl v5.42.0, dated 2026-01-17, which is also the last line of the Type::T...ibuting(3) page before the vibe check ended. Mwah πŸ’‹

πŸ“¦ where this page comes from