You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey Stefan, thanks for writing this library - it works great! Do you have any utility or library code in FreeBusy that handles parsing the ISO8601 date values coming in from the AVS when a slot is defined as of type AMAZON.Date? In some cases, the incoming string isn't parse-able to a DateTime or DateTimeOffset (for example, if I say "this weekend" the slot value comes in a "2016-W29-WE" which doesn't work with DateTime.TryParse(). Reading the docs on AMAZON.Date I see several formats that likely won't parse. Just wondering if there was a good mechanism for handling this in .NET, or if you just ended up parsing the incoming value for some known regex patterns. Thanks again for putting the time into creating this library!
The text was updated successfully, but these errors were encountered:
In a future release I'll contribute our parsing code to the library. It doesn't cover 100% of the standard, but we do handle the most frequent patterns.
Yesterday I submitted a pull request with code that parses the amazon date format. It handles all of the cases covered in the Amazon docs (except seasons) and few that show up but aren't mentioned in the docs.
I wrote this for my app. The AmazonSkillKit was such a time saver for me, I figured I'd contribute.
Hey Stefan, thanks for writing this library - it works great! Do you have any utility or library code in FreeBusy that handles parsing the ISO8601 date values coming in from the AVS when a slot is defined as of type AMAZON.Date? In some cases, the incoming string isn't parse-able to a DateTime or DateTimeOffset (for example, if I say "this weekend" the slot value comes in a "2016-W29-WE" which doesn't work with DateTime.TryParse(). Reading the docs on AMAZON.Date I see several formats that likely won't parse. Just wondering if there was a good mechanism for handling this in .NET, or if you just ended up parsing the incoming value for some known regex patterns. Thanks again for putting the time into creating this library!
The text was updated successfully, but these errors were encountered: