proto+lnrpc: update gRPC-REST gateway to v1.8.6 - #3650
Conversation
There was a problem hiding this comment.
Why is this required? This version seems to support go modules.
There was a problem hiding this comment.
It's not required. That was left over from a trial with an older version. Fixed.
307af2a to
b6c7ff8
Compare
|
it would be nice if we can also mark all the string fields as deprecated now and remove them in 0.10 |
cfromknecht
left a comment
There was a problem hiding this comment.
nice, this actually reduces the size of our gateway code! LGTM 🔥
joostjager
left a comment
There was a problem hiding this comment.
it would be nice if we can also mark all the string fields as deprecated now and remove them in 0.10
Do we want to do this? I think it would be nice to be able to remove the string fields at some point
Yep, can be done in separate PR though. |
|
I am getting a new error: |
|
Nvm, needed to update dep |
Fixes #3168
When using the REST gateway, fields that have the type
bytesinrpc.protocannot be used in query or path parameters (see #552 which lead to workarounds like #592).The root cause of this is that the version of
grpc-gatewaywe use doesn't support mapping to[]byteyet.Trying to use
bytesparameters results in{"error":"unsupported field type uint8","code":3}.This has been fixed in grpc-ecosystem/grpc-gateway#489.
Unfortunately, we can't use the newest version of
grpc-gateway(which would be1.11.3at the moment) because that has a bug that messes up ourrpc.swagger.json(grpc-ecosystem/grpc-gateway#746).After some trial and error, I found that version
1.8.6is the newest version that works for our use case and produces the smallest diff in our generated code.