Samuel
@samuel.fm
ok I'm sorry but I've decided Swift sucks. tried to implement an OpenAPI client for the TfL Unified API and it doesn't work because Swift doesn't allow milliseconds in their time stamps??
2 9
BossettNSDate().timeIntervalSince1970 returns a TimeInterval which claims 'sub-millisecond precision over a range of 10,000 years' - so is this just ISO 8601 being annoying about fractional seconds?
TimeInterval | Apple Developer Documentation
A number of seconds.
developer.apple.com
SamuelFrom what I’ve seen, it’s actually Swift implementing a subset of the ISO spec by default when you use .withInternetDateTime
I think you can enable it with the .withFractionalSeconds format option but now I need to go digging around in the OpenAPI client code
2 6Samuelforums.swift.org/t/iso8601dat...
oh boy - turns out enabling that option makes the milliseconds *mandatory*
ISO8601DateFormatter fails to parse a valid ISO-8601 date
When encoding iso8601 dates you might want careful control of the format. When decoding iso8601 dates I think you want a lenient parser, especially if you're writing a parser that will be the default ...
forums.swift.org
Honza DvorskyThere's a shortcut for enabling it on your generated client: swiftpackageindex.com/apple/swift-...
swift-openapi-runtime Documentation – Swift Package Index
swiftpackageindex.com