I was trying to inspect the SwiftYNABError in my calling code but wasn't able to because it wasn't publicly available. Updated it's accessor to public.
It seems SwiftYNABError.apiError was never thrown by Client. The ErrorDetails and other infrastructure (unit tests and json files) was in place except the actual impl in the Client.swift 😊. If it's unable to create the ErrorDetails, will fallback to .httpError.
Hi @andrebocchini ,
SwiftYNABErrorin my calling code but wasn't able to because it wasn't publicly available. Updated it's accessor topublic.SwiftYNABError.apiErrorwas never thrown byClient. TheErrorDetailsand other infrastructure (unit tests and json files) was in place except the actual impl in the Client.swift 😊. If it's unable to create theErrorDetails, will fallback to.httpError.apiErroris expected.