Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DTSTAMP should be (partially) filtered in calendarDataMatch #10

Open
macosforgebot opened this issue Jul 12, 2010 · 2 comments
Open

DTSTAMP should be (partially) filtered in calendarDataMatch #10

macosforgebot opened this issue Jul 12, 2010 · 2 comments
Assignees
Milestone

Comments

@macosforgebot
Copy link

@macosforgebot macosforgebot commented Jul 12, 2010

douglm@… originally submitted this as ticket:386


DTSTAMP is equivalent to LAST-MODIFIED for entities without a METHOD so should be filtered for those tests. For example, tests in put.xml fail because the DTSTAMP value changes,

DTSTAMP from rfc5545:

   Purpose:  In the case of an iCalendar object that specifies a
      "METHOD" property, this property specifies the date and time that
      the instance of the iCalendar object was created.  In the case of
      an iCalendar object that doesn't specify a "METHOD" property, this
      property specifies the date and time that the information
      associated with the calendar component was last revised in the
      calendar store.
...
      In the case of an iCalendar object that specifies a "METHOD"
      property, this property differs from the "CREATED" and "LAST-
      MODIFIED" properties.  These two properties are used to specify
      when the particular calendar data in the calendar store was
      created and last modified.  This is different than when the
      iCalendar object representation of the calendar service
      information was created or last modified.

      In the case of an iCalendar object that doesn't specify a "METHOD"
      property, this property is equivalent to the "LAST-MODIFIED"
      property.
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Aug 1, 2011

@wsanchez originally submitted this as comment:1:⁠ticket:386

  • Radar deleted
  • Priority changed from 5: Not set to 2: Expected
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Nov 30, 2011

@wsanchez originally submitted this as comment:2:⁠ticket:386

  • Milestone set to Later
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.