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
I've implemented two SDK calls and the developer experience so far wasn't stellar. 😅
Passing parameters is verbose. Why does the client need to know which params are path params and which are query?
Response type seems to be buried in a larger FetchResponse type which is also quite verbose.
It's not straightforward to match a function and its response type, you have to look in responses -> content.
Some functions (e.g. getSupportedFiatCodes) return the data directly, some (e.g. getMasterCopies) wrap it in a { data, error } object. Ideally they should all return the data directly, and errors should be returned as proper HTTP errors.
The text was updated successfully, but these errors were encountered:
I've implemented two SDK calls and the developer experience so far wasn't stellar. 😅
getSupportedFiatCodes
) return the data directly, some (e.g.getMasterCopies
) wrap it in a{ data, error }
object. Ideally they should all return the data directly, and errors should be returned as proper HTTP errors.The text was updated successfully, but these errors were encountered: