MooseX...oercion(3pm)

💖 MooseX::Meta::TypeConstraint::ForceCoercion 💖

okay bestie, so this is a page from the User Contributed Perl Documentation, and it's filed under MooseX...oercion(3pm) — the manual name got squished by the man page formatter, but we know the truth: it's MooseX::Meta::TypeConstraint::ForceCoercion. She's the one who forces coercion when you're validating type constraints. No cap. ✨

---

✨ NAME ✨

MooseX::Meta::TypeConstraint::ForceCoercion — Force coercion when validating type constraints 💅

---

🌸 VERSION 🌸

version 0.01

---

🦋 SYNOPSIS 🦋

use MooseX::Types:::Moose qw/Str Any/;
use Moose::Util::TypeConstraints;
use MooseX::Meta::TypeConstraint::ForceCoercion;

# get any type constraint
my $tc = Str;

# declare one or more coercions for it
coerce $tc,
    from Any,
    via { ... };

# wrap the $tc to force coercion
my $coercing_tc = MooseX::Meta::TypeConstraint::ForceCoercion->new(
    type_constraint => $tc,
);

# check a value against new type constraint. this will run the type
# coercions for the wrapped type, even if the value already passes
# validation before coercion. it will fail if the value couldn't be
# coerced
$coercing_tc->check('Affe');

like literally look at that last line, 'Affe' is getting coerced whether it likes it or not 😭 the whole point is that coercion is mandatory, not optional.

---

💜 DESCRIPTION 💜

This class lets you wrap any Moose::Meta::TypeConstraint in a way that will force coercion of the value when you're checking or validating a value against it. it's giving "you WILL be coerced, periodt" energy 👑

---

🎀 ATTRIBUTES 🎀

type_constraint

The type constraint to wrap. All methods except for validate and check are delegated to the value of this attribute. so she's basically a lil bodyguard that hands off everything else to the wrapped type — but keeps validate and check for herself 💅

---

🌈 METHODS 🌈

check ($value)

Same as Moose::Meta::TypeConstraint::check, except it will always try to coerce $value before checking it against the actual type constraint. If coercing fails the check will fail, too. so like, no sneaking past the vibe check just because you already technically passed 🫶

validate ($value, $coerced_ref?)

Same as Moose::Meta::TypeConstraint::validate, except it will always try to coerce $value before validating it against the actual type constraint. If coercing fails the validation will fail, too.

If coercion was successful and a $coerced_ref references was passed, the coerced value will be stored in that. 🎁 so you can snag the glow-up'd version and keep it, iykyk.

---

🌟 AUTHOR 🌟

Florian Ragwitz <rafl@debian.org>

shoutout to Florian, the original main character 💖

---

📜 COPYRIGHT AND LICENSE 📜

This software is copyright (c) 2009 by Florian Ragwitz.

This is free software; you can redistribute it and/or modify it under the same terms as perl itself. 🌸

---

okay that's the whole page bestie, you ate it up 🍓 and just so we're keeping receipts: this was written up against perl v5.36.0, dated 2022-12-09, and the manual page is MooseX...oercion(3pm) — go forth and force some coercions, no cap 💅✨🦋