[Moose] Coerce and messages

[Moose] Coerce and messages

	Karen Etheridge
	Sep 28, 2014 at 11:52 pm

On Sun, Sep 28, 2014 at 01:27:53PM -0700, Bill Moseley wrote:
I'm going to build a request with HTTP::Request::Common and want to use its
existing methods (POST, PUT, GET, etc.)

I'm curious how to control the error message better when coercing.

I'm lost - what is the advantage to storing the HTTP request method as a
subref, vs. as a string?

this may be of use for your validation check:
https://metacpan.org/pod/MooseX::Types::HTTPMethod

Search Discussions

Discussion Posts

Bill Moseley: I'm going to build a request with HTTP::Request::Common and want to use its existing methods (POST, PUT, GET, etc.) I'm curious how to control the error message better when coercing. My class gets an HTTP method name as an attribute, and I wanted to validate it for how it will get used: subtype HttpMethod => as 'Str', where { HTTP::Request::Common->can( $_ ) }, message { "The method provided [$_] does not appear to be a valid HTTP method" }; has http_method => ( is => 'ro', isa => 'HTTPMethod',

Follow ups

Bill Moseley: No advantage, really. It was more of a learning exercise with Moose, not so much solving the specific problem. The code came from a non-Moose script that did this: my $sub = HTTP::Request::Common->can( $method ) my $req = $sub->( @args ); So, moving it over to Moose I wanted to provide some validation, so I created the HttpMethod subtype. subtype HttpMethod => as 'Str', where { HTTP::Request::Common->can( $_ ) }, message { "The method provided [$_] does not appear to be a valid HTTP method" }

Related Discussions

Discussion Navigation

view	thread \| post
posts	‹ prev \| 2 of 3 \| next ›

Discussion Overview

group	moose @
categories	perl
posted	Sep 28, '14 at 8:28p
active	Sep 29, '14 at 1:14a
posts	3
users	2
website	iinteractive.com...

font	variable	Hotkey: f
user style	avatars	Hotkey: a

[Moose] Coerce and messages

Search Discussions

Discussion Posts

Related Discussions

2 users in discussion