Currently, the event metadata for calendar events are being stored in the Google Calendar events' descriptions in JSON form. This has been an issue when attempting to manually modify the metadata for meetings (i.e. editing the event's description manually) as users can easily mess up proper formatting by missing a comma, quote, or by messing up whitespace.
Some fixes have been proposed:
Make the meeting edit command good enough so people don't get their grubby hands on the raw metadata
Use YAML instead of JSON (is this a good idea? YAML is whitespace-sensitive), making editing event descriptions a bit less error-prone
Fix up the JSON parser so doesn't complain when there's some whitespace somewhere
Currently, the event metadata for calendar events are being stored in the Google Calendar events' descriptions in JSON form. This has been an issue when attempting to manually modify the metadata for meetings (i.e. editing the event's description manually) as users can easily mess up proper formatting by missing a comma, quote, or by messing up whitespace.
Some fixes have been proposed:
meeting editcommand good enough so people don't get their grubby hands on the raw metadataDetermine the best option and implement it