mf192
Just mindblowing that companies don't adopt a schema-first approach to appeal to a broader customer base. I've lost count of the number of hnd rolled clients I've had to write over the years.
It gets even better if the API itself is backed by some RPC framework. With that, users can simply generate a client and get going.
It feels like we can do better as an industry, this cracked me up because it's so true.
"a single JSON example as the only documentation is... unfortunate"
https://github.com/bufbuild/connect-web/blob/main/packages/c...
I'm sure someone will chime in on the implementation details, but hopefully others can give it a try with their projects!
- no proxies - smaller bundle size - idiomatic TS code in both runtime and generated code - streaming - ... and more
Connect is for the rest of us. I wonder what kind of useful general-purpose interceptors folks will come up with?
It was the #3 issue opened on twirp repository, but they never settled on a solution.
https://github.com/twitchtv/twirp/issues/3
One super underrated feature Connect offers for Go devs is access to the request/response headers. No more plumbing incoming/outgoing context :phew: