Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OpenLibrary use a live books API to demo mapping RPC->REST.
The search service returns duplicate fields:
num_found
, at the top and bottom of a list. This fails with protojson: golang/protobuf#1568It would be useful for implementations to handle route by route mutations. Currently using the proxy to mutate request/respons. I think to support all the weirdness of REST apis we will have to give users lots of flexibility on translating.
Stripe
I didn't realize stripe doesn't accept JSON on POST... only url encoded values using their custom syntax: https://stripe.com/docs/api/payment_intents/create . See the first commit.
So this example is a dead end. It surprisingly works for creating and getting a payment intent if you don't use any fields with an
_
, but anything more complex won't be possible.