Breaking Change: Recurrence exception delimiter change

Thread is closed for posting
1 posts, 0 answers
  1. Kendo UI
    Kendo UI avatar
    322 posts
    Member since:
    Aug 2011

    Posted 07 Jun Link to this post

    From the official 2016 Q2 Release (2016.2.504) the Scheduler will start using comma (previously semicolon) as delimiter for the recurrence exceptions. Also the Scheduler will no longer add trailing delimiter to the recurrence exception.

    This change was required as the previous behavior does not conform to the RFC5545 spec:

    From the official 2016 Q2 Release (2016.2.504) the Scheduler will start using comma (previously semicolon) as delimiter for the recurrence exceptions. Also the Scheduler will no longer add trailing delimiter to the recurrence exception. This change driven by the RFC5545 spec (previous behavior was incorrect):


    http://tools.ietf.org/html/rfc5545#page-120
    The following changes are required to all events that have "recurrenceException" set:
    1. Remove the trailing semicolon delimiter
    2. Replace all occurrences of semicolon with comma
    //Old recurrence exception:
    recurrenceException:"20160603T050000Z;20160503T050000Z;"
      
    //New recurrence exception:
    recurrenceException:"20160603T050000Z,20160503T050000Z"

    Apologies for the caused inconvenience.
Back to Top