Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Path-Router CPAN distribution.

Report information
The Basics
Id: 78506
Status: open
Priority: 0/
Queue: Path-Router
People
Owner: Nobody in particular
Requestors: ether [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: 0.12
Fixed in: (no value)

History Show all quoted text
  Sat Jul 21 12:58:44 2012 ether [...] cpan.org - Ticket created
Subject: Path::Router::Route::ValidationMap should accept other type classes
Path::Router::Route::ValidationMap should be able to accept any type system that provides the proper interface. It is probably just as easy as adding another element to the OR in the class_type declaration: duck_type([ @methods ]) where @methods are the interfaces used by ValidationMap (e.g. 'check'). This gets me to thinking that maybe Moose's type system should define this duck_type itself, or even an interface role filled with requires() declarations, to specify what interface an alternative type system should adhere to. Let's discuss this on #moose-dev sometime, as it would dovetail nicely with Dave Rolsky's work on a new type system.
  Sat Jul 21 13:04:01 2012 ether [...] cpan.org - Correspondence added
Oh yeah, I forgot to mention my initial motivation for opening this - I wanted to use a MooseX::Types type here instead of a bare moose type string.
  Sat Jul 21 13:04:02 2012 ether [...] cpan.org - Status changed from 'new' to 'open'
  Sun Jul 22 01:46:09 2012 ether [...] cpan.org - Correspondence added
On Sat Jul 21 10:04:01 2012, ETHER wrote: Show quoted text
> Oh yeah, I forgot to mention my initial motivation for opening this - I > wanted to use a MooseX::Types type here instead of a bare moose type
string. MooseX::Types type names work as-is; presumably other competing type systems (are there any in production yet?) would work as well. Therefore the only work to be done is to mention this capability in documentation. :)