make GEO property RFC 5545 compliant #74
Merged
Conversation
This file contains 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
| @@ -197,7 +197,7 @@ class Event extends Component | |||
|
|
|||
| /** | |||
| * Dates to be excluded from a series of events. | |||
| * | |||
| * | |||
There was a problem hiding this comment.
There has been an empty space here that was being kicked by the editor on saving.
sgehrig
changed the title
|
Looks good to me! 👍 |
|
Fixed in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
this should fix issue #73 for Google Calendar as it changes the
GEOproperty to be RFC 5545 compliant.This is a very naive fix but it's the easiest solution without requiring more changes.