Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic

Re: constraining the keys of a HashRef in Moose

by kennethk (Abbot)
on Aug 29, 2013 at 15:30 UTC ( #1051463=note: print w/replies, xml ) Need Help??

in reply to constraining the keys of a HashRef in Moose

IMHO you are thinking about this problem incorrectly. If you are using an object framework, then you should probably be using an object if you need a complex data behavior. This means scores should be a subtype with fields that are the allowed values, perhaps like:
#!/usr/bin/perl package Test::HashK; use Moose; use Moose::Util::TypeConstraints; our @_allowed_colors = qw(red green blue); enum 'colors', \@_allowed_colors; has scores => ( is => 'rw', isa => 'Test::HashK::Score', default => su +b{Test::HashK::Score->new()} ); # I want the allowed *keys* to be col +ors package Test::HashK::Score; use Moose; for my $color (@Test::HashK::_allowed_colors) { has $color => is => 'rw', isa => 'Num', ; } 1;

If you do want to keep it as an explicit hash, rather than a blessed object, you could use Hash::Util's lock_keys or lock_ref_keys:

my @colors = qw(red green blue); enum 'colors', \@colors; has scores => ( is => 'rw', isa => 'HashRef', default => sub { use Hash::Util 'lock_keys'; my %hash; lock_keys %hash, @colors; return \%hash; } );
Of course, the user could easily bypass this by inserting their own value. As with most things in Perl, it gives you all the rope you want, and if you want to work outside provided frameworks, that's your issue.

#11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1051463]
Jar. Jar!...

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (5)
As of 2017-04-25 12:53 GMT
Find Nodes?
    Voting Booth?
    I'm a fool:

    Results (453 votes). Check out past polls.