Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Expose `inputParser` on `Procedure`?
See original GitHub issueHi - have just started using trpc and it is 👌
One request: what do you think about exposing the (zod) schema on the Procedure object? The use-case being, I would like to create a UI in an internal admin app using react-json-schema-form for various whitelisted “admin” queries/mutations. If we could access appRouter._def.queries.myQuery.inputParser we could pass it to zod-to-json-schema which would give us some schemas we could use with react-json-schema-form.
It’s possible to do now by suppressing the typescript error about using a private field, but I wanted to see if you’d be open to making it public so that it wouldn’t disappear and break our workflow in a minor update.
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@mmkal - I’ll leave the PR + docs to you then. Would be really cool get an example of this up and running on retool, such a timesaver.
On phone, will give example tomorrow, but