Conversation
|
Related to #1 |
|
What is the purpose of this PR? You mention it's "for .catch()", but these methods already propagate errors via "await" |
|
@shrimpy-dev so you should return
|
|
Right, we aren't always expecting data. Using your examples, you expect a list of strings back from Now that you mention it, I see a number of places where we should replace |
@shrimpy-dev, not "replace return await with simply await.", need replace "simply await" with "return ..." or "return await ...". See your official API documentation, for example https://developers.shrimpy.io/docs/#naming-a-user And see code: shrimpy-node/lib/client/shrimpy-api-client.ts Lines 239 to 245 in e8bf841 This code does not responsing { "success": true }, it's responsing nothing. |
|
Right, the docs cover the request/response data. Just because In the docs you linked, you can see the expected usage is Is there a reason that you want the |
Note: async functions should return pure call, not await (for .catch()).