Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sometimes we got an event with DESCRIPTION contains colon as below:
BEGIN:VEVENT
UID:calendar.855.field_calendar_dates.0
CREATED:20170120T174441Z
DESCRIPTION:Bingo every Tuesday and Friday\n11:00 am - 2:00 pm\nAt the Fran
kfort Township Community Room\nCall for more information 815-806-2776
DTSTART;TZID=America/Chicago:20170502T110000
DTEND;TZID=America/Chicago:20170502T110000
LAST-MODIFIED:20170120T174441Z
SUMMARY:Senior Bingo
URL;TYPE=URI:http://www.frank.com/node/855
END:VEVENT
currently the parser split each line in two parts key and value , and its split by colon , so when we have multiple colons in the description line as above , the parser will take a part of it .
the fix is to take all the text after the first colon and set it in value variable