fitbit's swagger specs defines 'intraday' as operationid for many activity related operations

[omatrot]

When generating client code from fitbit's swagger specs, there is a problem because operationid is not unique among the operations.

Multiple activity related operations have the same operationid specified as 'intraday'.

Code generators are forced to generate a method name from the operation path that is normalised.

Because fitbit's operation paths starts with a digit (1), invalid function names are generated.

Could you fix your swagger specs ?

Thanks in advance.

Kind Regards,

Olivier MATROT.

[DavidSFitbit · Accepted solution]

Hey @omatrot, thanks for calling this out! We'll get a fix in as soon as possible.