ical_properties dataset - as list

[Robinlovelace]

I created the dataset ic_properties to show properties (equivalent of keys in key-value pairs) allowed (I think this is all of them):

ical::ic_properties
#>  [1] "CALSCALE"     "METHOD"       "PRODID"       "VERSION"     
#>  [5] "ATTACH"       "CATEGORIES"   "CLASS"        "COMMENT"     
#>  [9] "DESCRIPTION"  "GEO"          "LOCATION"     "PERCENT"     
#> [13] "PRIORITY"     "RESOURCES"    "STATUS"       "SUMMARY"     
#> [17] "COMPLETED"    "DTEND"        "DUE"          "DTSTART"     
#> [21] "DURATION"     "FREEBUSY"     "TRANSP"       "TZID"        
#> [25] "TZNAME"       "TZOFFSETFROM" "TZOFFSETTO"   "TZURL"       
#> [29] "ATTENDEE"     "CONTACT"      "ORGANIZER"    "RECURRENCE"  
#> [33] "RELATED"      "URL"          "UID"          "EXDATE"      
#> [37] "RDATE"        "RRULE"        "ACTION"       "REPEAT"      
#> [41] "TRIGGER"      "CREATED"      "DTSTAMP"      "LAST"        
#> [45] "SEQUENCE"     "REQUEST"      "FLOAT"        "INTEGER"     
#> [49] "AUDIO"        "DISPLAY"      "EMAIL"        "PUBLIC"      
#> [53] "PRIVATE"      "CONFIDENTIAL"

Created on 2018-08-11 by the reprex package (v0.2.0).

I think to make the 'key keys' easier we should create a named list, a bit like leaflet::providers which provides very useful auto-completion options illustrated below:

[layik]

+1

[Robinlovelace]

Update: I think I've found the 'core' properties of events - see here: https://github.com/ATFutures/ical/commit/9528bdffdc0ddbc0a06460495fb7782f4f066e15

[Robinlovelace]

@layik I saw you had a version of this dataset. Just checked and... happy to say it works!

Great fix!

[Robinlovelace]

I think only the commonly used 'core properties' benefit from being a named list, so keeping ic_properties unchanged.