Strict mode for reading/writing ical

[hukka]

Currently icalendar happily reads and writes data without all the fields required by the RFC. There should be a strict mode available, that does error checking.

[regebro]

I think a separate checker would be a better idea. It could be a part of icalendar, or separate.

[hukka]

That might work for reading, but for writing icalendar needs to be able to raise Exceptions when all required fields are not given.

[regebro]

What is the reason you can't just call a verification method before writing?

[hukka]

I wasn't even aware of a verification method. I tried looking for it in docs and source now, but still can't find it. Where is it?

[regebro]

There isn't one. Which is why I said "a" and not "the" verification method.
I take it that your answer to my question is that you could call one, and then I maintain my position that a checker would be a better idea than a strict mode.

[hukka]

Yes, anything that could make it certain that the files are valid according to spec (and thus at least hope for some interoperability).

[garbas]

@tpievila i would agree with @regebro to have checker/verification/validation method, just because it leaves implementing "strict" mode to users of library. but this is definetly something we should consider in next release (3.1)

[garbas]

oh and would be nice if somebody could champion this, since i'm not sure i'll have the time and enough free time in next months to be motivated to implement this (i just don't have a use-case for this so motivation for it is low).

[jacobSingh]

Is there a place where strict mode is defined? My exported cal isn't google compat and I'm not sure why.

[geier]

yes, RFC 5545

[niccokunzmann]

This is also related to #536