Service stub method generates without rpc parameter sometimes.

[adriangaro]

As the title says, got the following code generated, generate_geo_condition_sql_request missing from the method signature. From a quick look in code seems that sometimes the message does not exist in ServiceMethodCompiler.request.all_messages, py_input_message returning none and thus the jinja template not writing it.

class SqlStub(betterproto.ServiceStub):
    async def geo_conditions(
        self,
        *,
        timeout: Optional[float] = None,
        deadline: Optional["Deadline"] = None,
        metadata: Optional["MetadataLike"] = None
    ) -> "GenerateSqlResponse":
        return await self._unary_unary(
            "/csm.shaihulud.sql.SQL/geo_conditions",
            generate_geo_condition_sql_request,
            GenerateSqlResponse,
            timeout=timeout,
            deadline=deadline,
            metadata=metadata,
        )

Proto:

message GenerateGeoConditionSQLRequest {
  csm.common.RequestHeader header = 1;
  GenerateGeoConditionSQL payload = 2;
}
...
  
service SQL {
  rpc geo_conditions(GenerateGeoConditionSQLRequest) returns (GenerateSQLResponse);
  ...
}

Other grpc services work fine so am not sure what is causing in this case. Betterproto version 2.0.0beta5

[AlexanderZender]

Can subscribe to this, usually the first method in the stub is missing something

[paul-HDD]

Same here !

[AlexanderZender]

I found the issue or solution(?). @paul-HDD @adriangaro
When entering message class names or services and using capital letters 2 or 3 in a row this happens
change
GenerateGeoConditionSQLRequest -> GenerateGeoConditionSqlRequest
GenerateSQLResponse -> GenerateSqlResponse

this should fix the missing parameters, never more than 1 capital letter in a row is my personal rule now

[paul-HDD]

Thanks @AlexanderZender ! Confirmed this work locally for me.
Sounds like an issue to me as I cannot change the proto file 😓

[hf-kklein]

When entering message class names or services and using capital letters 2 or 3 in a row this happens
change

Can confirm. The problem is the casing. For a MWE see #438

[wpdonders]

Will be fixed by #436