You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the issue is the use of the type shared.UUID in a path parameter. I don't think we support this. The error message definitely needs improving, but I expect changing LocationID to string should fix your issue.
johanbrandhorst
changed the title
Error Message aggregate type TYPE_MESSAGE in parameter ... unclear
Poor error message when using message in path parameter
Dec 7, 2020
Hi @gunadhya, yes that seems like the place. I think for users that encounter this error we should make it clear that they can't use that protobuf type for a path parameter, and also maybe suggest a fix? How about
fmt.Errorf("%s.%s: %s is a protobuf message type. Protobuf message types cannot be used as path parameters, use a scalar value type (such as string) instead". meth.Service.GetName(), meth.GetName(), path)
📚 Documentation
--grpc-gateway_out: aggregate type TYPE_MESSAGE in parameter of ScheduleAPI.BookAppointment: LocationID
rpc looks like this
Given the example rpc and message I get the aforementioned error. I am unable to find any documentation on how to resolve this or what it means.
The text was updated successfully, but these errors were encountered: