Is your feature request related to a problem? Please describe.
The URL check requires variable names to be the same as name of the variables in proto files and not the JSON specific ones.
For example given that field type:
<name:"tenant_id" number:1 label:LABEL_OPTIONAL type:TYPE_STRING json_name:"tenantId" >
The urlHasVarsFromMessage uses tenant_id instead of tenantId which sounds like more reasonable as REST api.
Describe the solution you'd like
The function could check both names to ensure that URL parameters are available.
Is your feature request related to a problem? Please describe. The URL check requires variable names to be the same as name of the variables in proto files and not the JSON specific ones.
For example given that field type: <name:"tenant_id" number:1 label:LABEL_OPTIONAL type:TYPE_STRING json_name:"tenantId" >
The urlHasVarsFromMessage uses tenant_id instead of tenantId which sounds like more reasonable as REST api.
Describe the solution you'd like The function could check both names to ensure that URL parameters are available.