COMPLETED is strictly DATE-TIME

[Allen Winter]

Apologies.  I completely forgot about this for the 3.0.2 release.
Certainly we should have a graceful way of handling legacy ics files.

the application code should be fixed (perhaps with a conditional compile on libical3) to use the datetime value.

Milan, can you send me a legacy ics file I can play with?
This way, I'm sure what you need fixed.

I can make a 3.0.3 release easily enough.


On Tuesday, February 6, 2018 8:52:25 AM EST Milan Crha wrote:
> 	Hi,
> I just realized that since libical 3.0 the COMPLETED property is
> provided as strictly DATE-TIME, while previous versions (like 2.0)
> could save DATE there. I know RFC 5545 defines the property
> as DATE-TIME only, but there are plenty of already saved components
> which are DATE.
> 
> The worse is that when I try to save the date-only value into the
> COMPLETED property, then it is changed to:
> 
>    COMPLETED:00000000T000000
> 
> and when I read it back from the disk I receive:
> 
>    X-LIC-ERROR;X-LIC-ERRORTYPE=VALUE-PARSE-ERROR:Can't parse as DATE-TIME 
>     value in COMPLETED property. Removing entire property: 00000000T000000
> 
> and when I try to load the already saved DATE value, it's turned into:
> 
>    X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Invalid VALUE 
>     type for property COMPLETED: VALUE=DATE
> 
> That's pretty bad behaviour, breaking backward compatibility, and the
> most problematic I cannot just fix this on load, because it's the
> parses which breaks it first (or I do not know how to do that).
> 
> Is there any way to deal with this situation gracefully, please?
> 
> 	Thanks and bye,
> 	Milan
> 
> _______________________________________________
> libical-devel mailing list
> libical-devel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/libical-devel
> 


-- 
Allen Winter | allen.winter at kdab.com | Senior Software Engineer
KDAB (USA) LLC, a KDAB Group company
Tel. USA +1-866-777-KDAB(5322) ext3
KDAB - The Qt, C++ and OpenGL Experts