Add Format

[emersion]

Closes: #10

[luxifer]

Looks great! Can you try to parse an ical fixture (from the folder), then format it with your method, and re parse what you format, just to make sure the parsed fixture and the parsed format are strictly equal? this way this parser/formater will be sort of turing complete

[emersion]

Unfortunately this won't work great, because a map is used to store fields, hence fields will get re-ordered. Preserving fields (and params) ordering would require adding some sort of map with a list of fields attached.

[emersion]

Ah, but you mean comparing the parsed values? Yeah, can definitely do that!

[luxifer]

Yes that's what I mean. Thanks ;) Florent Viel Le mar. 18 févr. 2020 à 11:30, Simon Ser <[email protected]> a écrit :

…

Ah, but you mean comparing the parsed values? Yeah, can definitely do that! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#13?email_source=notifications&email_token=AADGKBT64CBBDVEPNY7PDEDRDO2DDA5CNFSM4KTCIDAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMBN7HQ#issuecomment-587390878>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADGKBSBCN6NQPH2GQVUM2LRDO2DDANCNFSM4KTCIDAA> .

[emersion]

Hmm, so one issue is that there are two sources of truth: the Properties fields and the parsed fields (e.g. Event.Timestamp). When formatting a field, the parsed field value is currently used because it might have been updated by the user, however since some fields are redundant (Timestamp vs EndTime) the result won't be equal to the original.

I'm tempted to replace parsed fields with helper functions like net/mail.Header does.

[emersion]

Ended up writing my own lib.