On Jan 29, 2018, at 13:30 , Saagar Jha <[email protected]> wrote: > > Uhh…JSONDecoder swallows all of JSONSerialization’s errors and wraps it into > its own > <https://github.com/apple/swift/blob/e5fdc0955ce662bd929c7e1706d4a1f1d0f5d397/stdlib/public/SDK/Foundation/JSONEncoder.swift#L1097>. > I’m not sure this counts as “more detailed”.
Well, it presents all of JSONSerialization’s errors as DecodingError, but these are not all the DecodingErrors it can present. Also, AFAICT from a brief look at that code, DecodingError has a “codingPath” value that apparently locates the error within the source string. That seems unique to JSONDecoder. OTOH, it may be that JSONSerialization errors are in fact as informative as JSONDecoder errors, in which case I mostly retract my comment. (I still think JSONDecoder is a better choice.) _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
