Date attribute is not typed correctly
Reported by Ben Hood | April 28th, 2011 @ 02:45 PM | in 0.9.3
The typedAttribute function in the RangeCategoryParser does not have a case for the date type - hence it gets cast down as a string type in the catch all block. Potentially we should consider throwing an exception when this kind of thing occurs instead of just coalescing it to a string.
Comments and changes to this ticket
-
Ben Hood April 28th, 2011 @ 04:09 PM
(from [80dabeada6753533dd2b313f14f1d235f9533c74]) [#211] Added case for date attributes https://github.com/lshift/diffa/commit/80dabeada6753533dd2b313f14f1...
-
Ben Hood April 28th, 2011 @ 04:32 PM
- State changed from “open” to “resolved”
- Assigned user changed from “Ben Hood” to “Paul Jones”
This has been merged into master, but it may require some post QA.
-
Ben Hood May 11th, 2011 @ 08:54 AM
- State changed from “resolved” to “closed”
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 ยป
A Real Time Differencing Tool.
People watching this ticket
Ben Hood
Referenced by
-
211
Date attribute is not typed correctly
(from [80dabeada6753533dd2b313f14f1d235f9533c74])
[#211] ...