Page MenuHomePhorge

Fixed the datetime format for MeetingRequests
ClosedPublic

Authored by mollekopf on Aug 14 2023, 5:15 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Apr 11, 1:41 AM
Unknown Object (File)
Mon, Apr 8, 1:59 PM
Unknown Object (File)
Sun, Apr 7, 10:01 AM
Unknown Object (File)
Wed, Apr 3, 1:26 PM
Unknown Object (File)
Wed, Apr 3, 1:26 PM
Unknown Object (File)
Wed, Apr 3, 1:26 PM
Unknown Object (File)
Mon, Mar 25, 2:16 AM
Unknown Object (File)
Sun, Mar 24, 6:33 AM
Subscribers
None

Details

Summary

It's supposed to be like this:

<StartTime>2023-08-15T11:00:00.000Z</StartTime>

Diff Detail

Repository
rS syncroton
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

mollekopf created this revision.

Tested with android, where it now displays the correct time. I'm relatively sure we could remove the globalid shenanigans again, but who knows for sure.

globalObjId is a required element, so we should not remove it.

This revision is now accepted and ready to land.Aug 14 2023, 6:33 PM

globalObjId is a required element, so we should not remove it.

I don't mean the globalObjId itself, just that we encode the year/month/date/now is probably useless as it seems to be treated as an opaque blob (which would make sense). Maybe these values are just in there as an ad-hoc uuid mechanism that is supposed to guarantee uniqueness.. in any case, I'll leave it for the time being.

This revision was automatically updated to reflect the committed changes.