New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC: Remove response wrapper #131
Comments
Out of interest, could you explain a little more regarding your use-case and constraints? I'm keen to hear some more opinions on this. I'm happy to remove our response wrapper as a breaking change in the next major Proposed response payload changesSuccess- {
- "ok": true,
- "data": "This is good"
- }
+ "This is good" Error{
- "ok": false,
- "error": {
- "message": "This is bad",
- "code": "BAD_REQUEST",
- "issues": [...]
- }
+ "message": "This is bad",
+ "code": "BAD_REQUEST",
+ "issues": [...]
} |
I'm implementing a REST endpoint in my app for any ln-url compliant bitcoin wallet. In this case i'm generating a withdrawal request and the wallets expect the response to have certain properties.
|
Hi @moogmodular, I have implemented this feature and released it under the |
i did and it works exactly as intended. thank you! |
@moogmodular - I'm just about the publish a new - "trpc-openapi": "^1.0.0-alpha.0"
+ "trpc-openapi": "1.0.0-alpha.0" (tl;dr - remove the |
hi!
i need to satisfy a REST call which i can't influence. is there a way to return the response without the wrapper:
instead of this:
return this:
if not, it would be a nice enhancement since i'm going to be not the only one with this issue. i'm probably going to fork this for now until i'm confident enough to make a PR.
The text was updated successfully, but these errors were encountered: