Custom Types are not automatically registered as custom
Reported by Ted Han (knowtheory) | September 10th, 2010 @ 08:46 PM
see: http://gist.github.com/574648#comments
In essence, the Integer validations are being fired on a property that inherits from Integer, but is not represented to the user as an Integer. As a result the validations system is throwing an error incorrectly.
(ChromeEpochTime was copied nearly verbatim from dm-types EpochTime)
Comments and changes to this ticket
-
Piotr Solnica (solnic) March 24th, 2011 @ 06:00 AM
- State changed from “confirmed” to “not-applicable”
This will be improved with finalized Property API. Now you just need to override valid? and/or primitive? in case of custom complex types.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Piotr Solnica (solnic)