Someone working on the backend (not ts/js) code wrote console.log out of habit instead of whatever the right thing is for their environment (error_log, etc), and the error handling managed to bubble up the error from the backend to the frontend somehow

oooh, shame on me for not keeping up to date!

Very nice to see this, thank you very much!

I think the advantages of automatically generated api libs are pretty hard to ignore (keeping your types in sync between your api/ui, etc), but the niceties of rtk query are similarly hard to ignore. I’d like a talk on how to best capture the advantages of both.

I’m definitely not communicating this effectively :) Let me try putting it this way: I would love to attend a talk on how to autogenerate rtk query hooks from an openapi file (a workflow that I don’t think currently exists), best practices when doing this, common problems/solutions, etc.

So we have these two ways of doing the same thing, but with different tradeoffs.

What I’m referring to as a disconnect is that rtk query provides a great way to generate funcs (in the form of hooks) for accesing an api; and that there are a number of great libs for generating funcs for accessing an api by deriving them from an openapi json/yaml file. Not a concern per se.

I don’t know how this would coalesce into a talk, but I think there’s a real disconnect between what rtk query provides (which I’m _very_ happy with) and what openapi provides. Is there anything on your mind re: automatically generating hooks via rtk query from an openapi json/yaml file?