Support using FieldMasks with GET requests

[kibertoad]

Some GET requests (e. g. search) benefit greatly from being able to distinguish between default (e. g. 0) and non-defined values, since searching by "name='John' && age = 0" is not the same as "name='John' && age = undefined".
Since FieldMasks are a generally recommended approach for optional fields in gRPC, it would be super helpful if grpc-gateway would support that.

[ivucica]

While it's recommended to use proto3 (so your FR makes sense), have you tried using proto2 syntax to distinguish between default and undefined values?

[johanbrandhorst]

This is being worked on in #671

[kibertoad]

@johanbrandhorst Are you sure? There was explicit request to create a separate issue as implementation would have to be handled separately.

[johanbrandhorst]

How is your request different from that being implemented in #671? I apologize if I've misunderstood.

[kibertoad]

#671 very explicitly handles specific case of "If a binding is mapped to PATCH [HTTP method]". This issue is about GET HTTP methods.

[johanbrandhorst]

Good spot, this'll have to be a separate PR then. Sorry for the misunderstanding.

[kibertoad]

@johanbrandhorst Could you please remove "duplicate" label then :)?

[kibertoad]

Ah, thanks, already done.

[negativeOne1]

hey, just wanted to ask if there are any updates on this one? Could really use this feature.

[johanbrandhorst]

Be the change you want to see! What can I do to help you get this in?