Alan
Not sure if this will help, but here's how I implemented this for a project I worked on: ``` extension NSDate: Decodable { public static func decode(json: AnyObject) throws ->...
Looks like this lib is going to have to do the Enum namespace hack, and come up with something besides `Decodable` for the namespace.
Edit: I have no idea what I was talking about here, obviously the decode function I gave would need to take an additional parameter in my example. DELETED
If Decodable wants to solve this problem, it may be an idea to explore adding an 'or' operator. I'll do some exploration, but it would look like this at the...
Thinking about the problem further, I don't think it's going to be possible for my above syntax to work, as the => operator will either throw, or it won't, and...
From an implementation standpoint, my above suggestion seems ... rather complex, bordering on unmaintainable/untenable/impractical. I started an exploration into what would be required, and it involves changing the path string...
At first blush, I am not a fan of these changes. Not that they are bad solutions, but that they are adding complexity for the common case. My concern is...
Sounds like a plan, make it so!
I don't think so, it should still work if you have the cached auth. You could always try just changing the path in the source and recompiling.